Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 808e6d897e27e8f7f9a4f7292ee8c59a362d0005591f8d2624b8b865e6902681

Tx prefix hash: cecd887b9ba15ced53b715b00ae9144ba85eafeb7ce416d1176605c539c384d8
Tx public key: 10dcb7f4f33c57d608a93caa969fefd78829196a33ae56e24e456ecbd8f194f3
Timestamp: 1704721536 Timestamp [UCT]: 2024-01-08 13:45:36 Age [y:d:h:m:s]: 01:140:05:14:19
Block: 930885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361345 RingCT/type: yes/0
Extra: 0110dcb7f4f33c57d608a93caa969fefd78829196a33ae56e24e456ecbd8f194f302110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4de9c91e6d2668f6e749fb50a5776ec064616814146de41585a17cda5c0756a0 0.600000000000 1388775 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": 930895, "vin": [ { "gen": { "height": 930885 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4de9c91e6d2668f6e749fb50a5776ec064616814146de41585a17cda5c0756a0" } } ], "extra": [ 1, 16, 220, 183, 244, 243, 60, 87, 214, 8, 169, 60, 170, 150, 159, 239, 215, 136, 41, 25, 106, 51, 174, 86, 226, 78, 69, 110, 203, 216, 241, 148, 243, 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