Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56861e0da81a4e32c4e78b415011747b3da5b224fed2e35e14ab17db22cda2f7

Tx prefix hash: c0597e5dbd6ddd11852294b1d887c546fdac948cb4336e648ce794bfefd7907a
Tx public key: 74dfd37da804f2978d9e3d845a156b0a8f7cf7f6ff8f348c9a083463c0e63edd
Timestamp: 1733903729 Timestamp [UCT]: 2024-12-11 07:55:29 Age [y:d:h:m:s]: 00:104:22:17:57
Block: 1172728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74757 RingCT/type: yes/0
Extra: 0174dfd37da804f2978d9e3d845a156b0a8f7cf7f6ff8f348c9a083463c0e63edd021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e404c0ba6be162522ecb2ddc9e6dfb349343b31fd7a132475a19322c2b2b09a6 0.600000000000 1658657 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": 1172738, "vin": [ { "gen": { "height": 1172728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e404c0ba6be162522ecb2ddc9e6dfb349343b31fd7a132475a19322c2b2b09a6" } } ], "extra": [ 1, 116, 223, 211, 125, 168, 4, 242, 151, 141, 158, 61, 132, 90, 21, 107, 10, 143, 124, 247, 246, 255, 143, 52, 140, 154, 8, 52, 99, 192, 230, 62, 221, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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