Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 649f580c1f61efb26bc6ede52db8c346d29330ca07e9481d4c7d90d3096410c8

Tx prefix hash: c4c64cd11542f3a7ed229b47bf53b749177510e022b8894ace68bb4ca161920e
Tx public key: 2a5884c385105671d9a748352b63292a24639a575b54a0fff0b1f5be3240a0bf
Timestamp: 1682525151 Timestamp [UCT]: 2023-04-26 16:05:51 Age [y:d:h:m:s]: 01:302:17:33:56
Block: 747116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477578 RingCT/type: yes/0
Extra: 012a5884c385105671d9a748352b63292a24639a575b54a0fff0b1f5be3240a0bf021100000003b3164c24000000000000000000

1 output(s) for total of 2.053500234000 dcy

stealth address amount amount idx
00: 40c2f051b4da88a20b35cb1a1d507bd8f97d4ff0010a6ba633836f77e7a33705 2.053500234000 1194755 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": 747126, "vin": [ { "gen": { "height": 747116 } } ], "vout": [ { "amount": 2053500234, "target": { "key": "40c2f051b4da88a20b35cb1a1d507bd8f97d4ff0010a6ba633836f77e7a33705" } } ], "extra": [ 1, 42, 88, 132, 195, 133, 16, 86, 113, 217, 167, 72, 53, 43, 99, 41, 42, 36, 99, 154, 87, 91, 84, 160, 255, 240, 177, 245, 190, 50, 64, 160, 191, 2, 17, 0, 0, 0, 3, 179, 22, 76, 36, 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