Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b2c796dfd90067d38e0d8c9ca5c67fb490d830ee66ad37cfbb7dc951da5d56f

Tx prefix hash: fa5bc15b850652fe5a90dbb4418fd2b4013df7e29e2b2855555c4eceb27d0737
Tx public key: 62563df7336cdfc83b7b705bf855aa497da4d14cc0ac92f7b96f23cee5964570
Timestamp: 1707640187 Timestamp [UCT]: 2024-02-11 08:29:47 Age [y:d:h:m:s]: 01:268:07:30:49
Block: 955077 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 450519 RingCT/type: yes/0
Extra: 0162563df7336cdfc83b7b705bf855aa497da4d14cc0ac92f7b96f23cee596457002110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dea626161753a2f183bec7c54a259fd7c41bbf751de0bbb936ffb05c82906dbc 0.600000000000 1414359 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": 955087, "vin": [ { "gen": { "height": 955077 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dea626161753a2f183bec7c54a259fd7c41bbf751de0bbb936ffb05c82906dbc" } } ], "extra": [ 1, 98, 86, 61, 247, 51, 108, 223, 200, 59, 123, 112, 91, 248, 85, 170, 73, 125, 164, 209, 76, 192, 172, 146, 247, 185, 111, 35, 206, 229, 150, 69, 112, 2, 17, 0, 0, 0, 5, 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