Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 960f7ca7b0b6682e7a92eef50e770f45d53e67fb152959b04869b110ffc171de

Tx prefix hash: a33ebfc6922ec905465bfed83896452965a58e0167ad303145968d1efb33a7d1
Tx public key: eedd4b3ec8ea20e4eb2b59a908bc5550c107d8c6093c24476488fec641c5a953
Timestamp: 1737058814 Timestamp [UCT]: 2025-01-16 20:20:14 Age [y:d:h:m:s]: 00:151:23:13:10
Block: 1198833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108317 RingCT/type: yes/0
Extra: 01eedd4b3ec8ea20e4eb2b59a908bc5550c107d8c6093c24476488fec641c5a953021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3de2f7bd0e8cef78dc37c8d60aee7b8d03b3abd234e7cfd05d2a529e84a3eee8 0.600000000000 1685460 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": 1198843, "vin": [ { "gen": { "height": 1198833 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3de2f7bd0e8cef78dc37c8d60aee7b8d03b3abd234e7cfd05d2a529e84a3eee8" } } ], "extra": [ 1, 238, 221, 75, 62, 200, 234, 32, 228, 235, 43, 89, 169, 8, 188, 85, 80, 193, 7, 216, 198, 9, 60, 36, 71, 100, 136, 254, 198, 65, 197, 169, 83, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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