Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73d000e03fdff8c706b32e75ce26ae335ee9c2ddab22eb793525fd57134b19f3

Tx prefix hash: dca10a9f269b5153001be4d0f7ae146caad04d3b8f428c5d88c339bbdab966a7
Tx public key: d0925c3ee9bb636e0af59614f9621004654489e5ce2d9c303eeb6317763c9d3a
Timestamp: 1703895384 Timestamp [UCT]: 2023-12-30 00:16:24 Age [y:d:h:m:s]: 01:133:14:59:17
Block: 924032 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356643 RingCT/type: yes/0
Extra: 01d0925c3ee9bb636e0af59614f9621004654489e5ce2d9c303eeb6317763c9d3a02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d75b1f3ea47a487898b5410956523771715ba6b2ed16bcaa385d9c15a0693b75 0.600000000000 1381774 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": 924042, "vin": [ { "gen": { "height": 924032 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d75b1f3ea47a487898b5410956523771715ba6b2ed16bcaa385d9c15a0693b75" } } ], "extra": [ 1, 208, 146, 92, 62, 233, 187, 99, 110, 10, 245, 150, 20, 249, 98, 16, 4, 101, 68, 137, 229, 206, 45, 156, 48, 62, 235, 99, 23, 118, 60, 157, 58, 2, 17, 0, 0, 0, 6, 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