Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc12215698685913c48e42292e9b1e4be231ba658e59fff83a25f6e1a65b7a20

Tx prefix hash: 0eb61eb82b4670708fad2b09f88f9602103da6d9d3d891c19fe7bff8e92a31cb
Tx public key: fd1863f0493affba3baf4f91b7dba3fda1dcf3d14c9183795ed5ae94794a2f40
Timestamp: 1719215255 Timestamp [UCT]: 2024-06-24 07:47:35 Age [y:d:h:m:s]: 00:274:07:24:50
Block: 1051039 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196009 RingCT/type: yes/0
Extra: 01fd1863f0493affba3baf4f91b7dba3fda1dcf3d14c9183795ed5ae94794a2f4002110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e337e3b9cdadc455fcfed489ec1b735f954e2f7e6ca9d90048109d21638ec16b 0.600000000000 1521226 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": 1051049, "vin": [ { "gen": { "height": 1051039 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e337e3b9cdadc455fcfed489ec1b735f954e2f7e6ca9d90048109d21638ec16b" } } ], "extra": [ 1, 253, 24, 99, 240, 73, 58, 255, 186, 59, 175, 79, 145, 183, 219, 163, 253, 161, 220, 243, 209, 76, 145, 131, 121, 94, 213, 174, 148, 121, 74, 47, 64, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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