Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 971253108d98eb729376a4b82327ffefdc7de3ee24ddc3d0454ca66333bce531

Tx prefix hash: 90d0348ba733c1667d4dac552f45e4914a3a39d240c16454d166f0b6f2f989e3
Tx public key: 6a3888a943c1726e3be88f8a2e0381dc116a32033a6daa924e8c25ef03b5499e
Timestamp: 1712315163 Timestamp [UCT]: 2024-04-05 11:06:03 Age [y:d:h:m:s]: 00:351:13:41:24
Block: 993818 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251373 RingCT/type: yes/0
Extra: 016a3888a943c1726e3be88f8a2e0381dc116a32033a6daa924e8c25ef03b5499e02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba670cc317582d3d3d89340020659ea3e6ccbae0185063ac7f2be2836b08c136 0.600000000000 1454206 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": 993828, "vin": [ { "gen": { "height": 993818 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba670cc317582d3d3d89340020659ea3e6ccbae0185063ac7f2be2836b08c136" } } ], "extra": [ 1, 106, 56, 136, 169, 67, 193, 114, 110, 59, 232, 143, 138, 46, 3, 129, 220, 17, 106, 50, 3, 58, 109, 170, 146, 78, 140, 37, 239, 3, 181, 73, 158, 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