Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc186e456250e18cb877e4f93e121bd94b4621f99e1abb28a1624c42286e87ef

Tx prefix hash: 77331f9a643cb76ecc315c79f4a51ec23351f945a30e74f150c270087bfdf0ee
Tx public key: cdc8c194fece37892f8b642a8a74c101f619aa5ded6f38f2e18076fb03bd95c7
Timestamp: 1711049945 Timestamp [UCT]: 2024-03-21 19:39:05 Age [y:d:h:m:s]: 01:000:09:00:17
Block: 983372 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261222 RingCT/type: yes/0
Extra: 01cdc8c194fece37892f8b642a8a74c101f619aa5ded6f38f2e18076fb03bd95c702110000000c0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 163c5b7e94f58853be54266bad307a2d908e5e9bbb900a5edbe18ecb04a29e6e 0.600000000000 1443499 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": 983382, "vin": [ { "gen": { "height": 983372 } } ], "vout": [ { "amount": 600000000, "target": { "key": "163c5b7e94f58853be54266bad307a2d908e5e9bbb900a5edbe18ecb04a29e6e" } } ], "extra": [ 1, 205, 200, 193, 148, 254, 206, 55, 137, 47, 139, 100, 42, 138, 116, 193, 1, 246, 25, 170, 93, 237, 111, 56, 242, 225, 128, 118, 251, 3, 189, 149, 199, 2, 17, 0, 0, 0, 12, 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