Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12e3eeadde94f5439c09fc458b8bb1b015aa9e0015cc9b930bfb21b0c1973f14

Tx prefix hash: bc6986f8217c8ae7b7aca9bf4738b067c53caeb33e9bb20da09036a6c2d7fef5
Tx public key: c3c1ab2d1da7d43cb37df2098090df90a17763587a4af4f4c96e48d1047cc532
Timestamp: 1703034284 Timestamp [UCT]: 2023-12-20 01:04:44 Age [y:d:h:m:s]: 01:113:20:10:29
Block: 916904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342497 RingCT/type: yes/0
Extra: 01c3c1ab2d1da7d43cb37df2098090df90a17763587a4af4f4c96e48d1047cc53202110000000b75e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb6e12fc6dd5ff4c257fb22baec3a624edc8d6c3fef34a4df85bfa462d91d7a4 0.600000000000 1374466 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": 916914, "vin": [ { "gen": { "height": 916904 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb6e12fc6dd5ff4c257fb22baec3a624edc8d6c3fef34a4df85bfa462d91d7a4" } } ], "extra": [ 1, 195, 193, 171, 45, 29, 167, 212, 60, 179, 125, 242, 9, 128, 144, 223, 144, 161, 119, 99, 88, 122, 74, 244, 244, 201, 110, 72, 209, 4, 124, 197, 50, 2, 17, 0, 0, 0, 11, 117, 227, 240, 233, 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