Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5f7ab02dd1fe4af639ce12f290a92ad57b46fc6d92cde14763572318dd9be93

Tx prefix hash: d69e5e8b202decd9a09b1973d226b85f0c7173955d23b13115fffec9034c7f2c
Tx public key: e2c80b991b23b37a9ee0e638e2c9a33ae882696150135b76f0431d0bb357ecfd
Timestamp: 1715651138 Timestamp [UCT]: 2024-05-14 01:45:38 Age [y:d:h:m:s]: 00:242:13:14:58
Block: 1021497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173602 RingCT/type: yes/0
Extra: 01e2c80b991b23b37a9ee0e638e2c9a33ae882696150135b76f0431d0bb357ecfd02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2cf368c9a9ad9df3f4b43922c5a22de9918b67f8ebb69b65b78a34c23bfd584 0.600000000000 1485834 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": 1021507, "vin": [ { "gen": { "height": 1021497 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2cf368c9a9ad9df3f4b43922c5a22de9918b67f8ebb69b65b78a34c23bfd584" } } ], "extra": [ 1, 226, 200, 11, 153, 27, 35, 179, 122, 158, 224, 230, 56, 226, 201, 163, 58, 232, 130, 105, 97, 80, 19, 91, 118, 240, 67, 29, 11, 179, 87, 236, 253, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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