Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: fa8d7b2c5e1f04d3601850a28871697ea56e86f4d8bdb3a930e218679c6da400

Tx prefix hash: f02c1253884d7e8e55ed0de30787effecde14e90658d4cb9b3c4d8a39b3259d8
Tx public key: 8547fc594ac430e077d548cceff84d6561a665c0e78e93f9245a9bbbebe1d9a3
Timestamp: 1721308870 Timestamp [UCT]: 2024-07-18 13:21:10 Age [y:d:h:m:s]: 00:132:22:32:29
Block: 1068428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95108 RingCT/type: yes/0
Extra: 018547fc594ac430e077d548cceff84d6561a665c0e78e93f9245a9bbbebe1d9a302110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74d70906824f7c1704803a26e6204d5506f4fdcd50e6da8eb977f6f8fff6b3fa 0.600000000000 1539505 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1068438, "vin": [ { "gen": { "height": 1068428 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74d70906824f7c1704803a26e6204d5506f4fdcd50e6da8eb977f6f8fff6b3fa" } } ], "extra": [ 1, 133, 71, 252, 89, 74, 196, 48, 224, 119, 213, 72, 204, 239, 248, 77, 101, 97, 166, 101, 192, 231, 142, 147, 249, 36, 90, 155, 187, 235, 225, 217, 163, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8