Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9370fd1572d2b8e9c4ae16b2a0f90d29c59b23937fa364f365e62e75c723b58b

Tx prefix hash: 0fb695a4b364025c65c189422ceefa78b48e0bfc2964405ede2053511a7580a0
Tx public key: 2cef609364d261e937cebd4896569ba37bf0ccec6c4cb995d51a3f933ecd20de
Timestamp: 1742847361 Timestamp [UCT]: 2025-03-24 20:16:01 Age [y:d:h:m:s]: 00:312:08:10:47
Block: 1246482 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220888 RingCT/type: yes/0
Extra: 012cef609364d261e937cebd4896569ba37bf0ccec6c4cb995d51a3f933ecd20de02110000000524ff4ea1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 123c61ef5624952b83c329c3a9a681be5d48bb3e8c29e001e61acf36ed664e55 0.600000000000 1733483 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": 1246492, "vin": [ { "gen": { "height": 1246482 } } ], "vout": [ { "amount": 600000000, "target": { "key": "123c61ef5624952b83c329c3a9a681be5d48bb3e8c29e001e61acf36ed664e55" } } ], "extra": [ 1, 44, 239, 96, 147, 100, 210, 97, 233, 55, 206, 189, 72, 150, 86, 155, 163, 123, 240, 204, 236, 108, 76, 185, 149, 213, 26, 63, 147, 62, 205, 32, 222, 2, 17, 0, 0, 0, 5, 36, 255, 78, 161, 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