Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab905ac82bf74530399f7f96f4f72b521324c1790e6bf0d498245f812c7c7785

Tx prefix hash: 68ef61a7eefb6a4709f0fe024ec4e65e1467be48224d9ca9e74db2847284a759
Tx public key: 496f48bca064a00d69e7d2217baf715e9ec0d1d32f7e2426b17815906d59a6bd
Timestamp: 1713701994 Timestamp [UCT]: 2024-04-21 12:19:54 Age [y:d:h:m:s]: 00:360:23:43:51
Block: 1005339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258070 RingCT/type: yes/0
Extra: 01496f48bca064a00d69e7d2217baf715e9ec0d1d32f7e2426b17815906d59a6bd0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 235892329288d3d4622036d9b1723cb4deb01416f28cfac62fb5d77d6a3df168 0.600000000000 1465947 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": 1005349, "vin": [ { "gen": { "height": 1005339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "235892329288d3d4622036d9b1723cb4deb01416f28cfac62fb5d77d6a3df168" } } ], "extra": [ 1, 73, 111, 72, 188, 160, 100, 160, 13, 105, 231, 210, 33, 123, 175, 113, 94, 158, 192, 209, 211, 47, 126, 36, 38, 177, 120, 21, 144, 109, 89, 166, 189, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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