Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c50c1b9b2d344cfe424df10999eadfac160027ce457a72d1fe941e6365b5737

Tx prefix hash: 0310e85c10e3aae32c6fda68fb31402b1068a20262284c88b5fbda4208ff058f
Tx public key: d62b370c8570e8e7430f1338a1ce8bd82cc87a193bac7fb2729318b6c5abb3f8
Timestamp: 1713266992 Timestamp [UCT]: 2024-04-16 11:29:52 Age [y:d:h:m:s]: 01:267:09:48:07
Block: 1001718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 449875 RingCT/type: yes/0
Extra: 01d62b370c8570e8e7430f1338a1ce8bd82cc87a193bac7fb2729318b6c5abb3f802110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f69923891587244a4ed46c0cdceb4cb4059ac53747713d50515fc5a3e13efda6 0.600000000000 1462226 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": 1001728, "vin": [ { "gen": { "height": 1001718 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f69923891587244a4ed46c0cdceb4cb4059ac53747713d50515fc5a3e13efda6" } } ], "extra": [ 1, 214, 43, 55, 12, 133, 112, 232, 231, 67, 15, 19, 56, 161, 206, 139, 216, 44, 200, 122, 25, 59, 172, 127, 178, 114, 147, 24, 182, 197, 171, 179, 248, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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