Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2d0a169190e5128ae768cfb70fbdc6220a89c8c09f4678657bc8bc7d38c3652

Tx prefix hash: 16755a245ec6a3c604b79294cdf212fe01511a50b7243d4a54d8092646bddc4c
Tx public key: 985466a6a1b3b8e4f9d22c9850c0e4198b4cee1658c6140a75475f7844054967
Timestamp: 1733829858 Timestamp [UCT]: 2024-12-10 11:24:18 Age [y:d:h:m:s]: 00:117:04:07:49
Block: 1172116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83513 RingCT/type: yes/0
Extra: 01985466a6a1b3b8e4f9d22c9850c0e4198b4cee1658c6140a75475f7844054967021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b862e3a31c45ff47fc9bdba786113efc1565fb16570bdb5e2f58cc3330c219c2 0.600000000000 1657965 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": 1172126, "vin": [ { "gen": { "height": 1172116 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b862e3a31c45ff47fc9bdba786113efc1565fb16570bdb5e2f58cc3330c219c2" } } ], "extra": [ 1, 152, 84, 102, 166, 161, 179, 184, 228, 249, 210, 44, 152, 80, 192, 228, 25, 139, 76, 238, 22, 88, 198, 20, 10, 117, 71, 95, 120, 68, 5, 73, 103, 2, 17, 0, 0, 0, 2, 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