Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c27690e481ccb4669c60de3a9a0ede7246b8eb0d94c64c3ca52f19532216830e

Tx prefix hash: 399a1170b2162654b5c251e7018e0708e60ae91fdac7db21f56575a10387302d
Tx public key: 803b8584205817d3c95e91bae34f04faf7a3c2431eff8364ac0c7f6ab131935c
Timestamp: 1634807395 Timestamp [UCT]: 2021-10-21 09:09:55 Age [y:d:h:m:s]: 03:145:00:23:51
Block: 357348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 881686 RingCT/type: yes/0
Extra: 01803b8584205817d3c95e91bae34f04faf7a3c2431eff8364ac0c7f6ab131935c02110000000cfdc024ec000000000000000000

1 output(s) for total of 40.177229174000 dcy

stealth address amount amount idx
00: 0cd3f8253504142e77a126cc59d1a2857765b1272c951cf2e3196b8682b66a3c 40.177229174000 728704 of 0

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": 357358, "vin": [ { "gen": { "height": 357348 } } ], "vout": [ { "amount": 40177229174, "target": { "key": "0cd3f8253504142e77a126cc59d1a2857765b1272c951cf2e3196b8682b66a3c" } } ], "extra": [ 1, 128, 59, 133, 132, 32, 88, 23, 211, 201, 94, 145, 186, 227, 79, 4, 250, 247, 163, 194, 67, 30, 255, 131, 100, 172, 12, 127, 106, 177, 49, 147, 92, 2, 17, 0, 0, 0, 12, 253, 192, 36, 236, 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