Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f87baf44af6d0e0da4d41a93b4d9d3efe39cb9f2059a45f36422cc1b9a8a4ca

Tx prefix hash: 8180b558ca5831829e13701aebc24485685669b1cd3ff668569cec405aa4d05e
Tx public key: 1f7eb596bd628488a285882fabf0b63642a0ac50b8b91d8d799a95f9d4eadee0
Timestamp: 1717963263 Timestamp [UCT]: 2024-06-09 20:01:03 Age [y:d:h:m:s]: 00:316:09:01:05
Block: 1040669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226103 RingCT/type: yes/0
Extra: 011f7eb596bd628488a285882fabf0b63642a0ac50b8b91d8d799a95f9d4eadee00211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb3dcb51572e2495e36a342e0407cc1f34086639cf752e420ef8a3bc5f83b138 0.600000000000 1509326 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": 1040679, "vin": [ { "gen": { "height": 1040669 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb3dcb51572e2495e36a342e0407cc1f34086639cf752e420ef8a3bc5f83b138" } } ], "extra": [ 1, 31, 126, 181, 150, 189, 98, 132, 136, 162, 133, 136, 47, 171, 240, 182, 54, 66, 160, 172, 80, 184, 185, 29, 141, 121, 154, 149, 249, 212, 234, 222, 224, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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