Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 374130b32f877c842d36d0f9887fb32834641d70b7d6c6a0bd5104d46aa09d5a

Tx prefix hash: 5de228a0701528e8bc816283dfafa7ae38e429c3ee0cda005c81fae438d74dab
Tx public key: 7e1bd053dc42c50fb45d015814b6f48d6c2ec0156bc0ffcca5ed20a109c38827
Timestamp: 1708098372 Timestamp [UCT]: 2024-02-16 15:46:12 Age [y:d:h:m:s]: 01:098:12:11:16
Block: 958881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331478 RingCT/type: yes/0
Extra: 017e1bd053dc42c50fb45d015814b6f48d6c2ec0156bc0ffcca5ed20a109c388270211000000033f0590f7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24ac1a90b28164e241d99cb3a2550308ed8c3520851e468d4c704dae06d192b6 0.600000000000 1418308 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": 958891, "vin": [ { "gen": { "height": 958881 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24ac1a90b28164e241d99cb3a2550308ed8c3520851e468d4c704dae06d192b6" } } ], "extra": [ 1, 126, 27, 208, 83, 220, 66, 197, 15, 180, 93, 1, 88, 20, 182, 244, 141, 108, 46, 192, 21, 107, 192, 255, 204, 165, 237, 32, 161, 9, 195, 136, 39, 2, 17, 0, 0, 0, 3, 63, 5, 144, 247, 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