Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85b06b050342537282090b2fbbc52950a3172cb7d04d5e20940c8cd84c89d0ed

Tx prefix hash: b72fea734a5a2819119ea0230d8a550b7184f40f48a5d24f84de244df9a22db4
Tx public key: 647b84a71b1211c98468ab6190d1a330dd8ae0c4d9733c131a74224be6741b01
Timestamp: 1715071495 Timestamp [UCT]: 2024-05-07 08:44:55 Age [y:d:h:m:s]: 00:316:08:30:02
Block: 1016706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226136 RingCT/type: yes/0
Extra: 01647b84a71b1211c98468ab6190d1a330dd8ae0c4d9733c131a74224be6741b0102110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91fc4d9aa3fea14bd1de7725ae581f73d77269622c1ae0e401b201cd9ae8abc5 0.600000000000 1480363 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": 1016716, "vin": [ { "gen": { "height": 1016706 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91fc4d9aa3fea14bd1de7725ae581f73d77269622c1ae0e401b201cd9ae8abc5" } } ], "extra": [ 1, 100, 123, 132, 167, 27, 18, 17, 201, 132, 104, 171, 97, 144, 209, 163, 48, 221, 138, 224, 196, 217, 115, 60, 19, 26, 116, 34, 75, 230, 116, 27, 1, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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