Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b195bd478d4267b4b638579769146f2750170cbba81f1db2ced03719c2ac3b0

Tx prefix hash: 6d1fb3c2256db8922951bdb5b092b12f3d875ec7a91807325b53e28cabf378ad
Tx public key: 6e0777654ae052aa1542d1a4d0c0de03e550ab0b9e8eaeb153c71466cdc61212
Timestamp: 1722034007 Timestamp [UCT]: 2024-07-26 22:46:47 Age [y:d:h:m:s]: 00:294:06:37:41
Block: 1074414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210254 RingCT/type: yes/0
Extra: 016e0777654ae052aa1542d1a4d0c0de03e550ab0b9e8eaeb153c71466cdc6121202110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f025ba9a4e6600779739ca2ecf7acdc77a94669190ce212e7adc23e891d69cb2 0.600000000000 1546927 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": 1074424, "vin": [ { "gen": { "height": 1074414 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f025ba9a4e6600779739ca2ecf7acdc77a94669190ce212e7adc23e891d69cb2" } } ], "extra": [ 1, 110, 7, 119, 101, 74, 224, 82, 170, 21, 66, 209, 164, 208, 192, 222, 3, 229, 80, 171, 11, 158, 142, 174, 177, 83, 199, 20, 102, 205, 198, 18, 18, 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