Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89e70daf14499aeb221bb9860c82efe9ff204b0784f9620fb3580bbd29643613

Tx prefix hash: c5f607ae3d24bf6fcf7399da73fe2081524e676a0dbb5dee11d944e08429a637
Tx public key: 95df44fa1a1c45a00ed9e30ca91347c45b4e6aa2ce1453a0e8c18705ca6cd2ce
Timestamp: 1715784410 Timestamp [UCT]: 2024-05-15 14:46:50 Age [y:d:h:m:s]: 00:126:11:03:45
Block: 1022614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90570 RingCT/type: yes/0
Extra: 0195df44fa1a1c45a00ed9e30ca91347c45b4e6aa2ce1453a0e8c18705ca6cd2ce0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d404cbaa037e134208b77e50e493a28bcba4b5f1936d07d4365f30bcbbdef39 0.600000000000 1487267 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": 1022624, "vin": [ { "gen": { "height": 1022614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d404cbaa037e134208b77e50e493a28bcba4b5f1936d07d4365f30bcbbdef39" } } ], "extra": [ 1, 149, 223, 68, 250, 26, 28, 69, 160, 14, 217, 227, 12, 169, 19, 71, 196, 91, 78, 106, 162, 206, 20, 83, 160, 232, 193, 135, 5, 202, 108, 210, 206, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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