Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8433aead80187927a9d5f39f2340dd8edab0132ec6e4c276f086fa4d2f291053

Tx prefix hash: 5fb38548010f821dd79ceffaed0029268b4461aa47f94b5aeb4658e1e3251a47
Tx public key: 19ab59021c085e9e4e831ebf67d853dadbda2c1fe31acd90f091297e223f2df0
Timestamp: 1706221406 Timestamp [UCT]: 2024-01-25 22:23:26 Age [y:d:h:m:s]: 01:147:06:04:41
Block: 943296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366216 RingCT/type: yes/0
Extra: 0119ab59021c085e9e4e831ebf67d853dadbda2c1fe31acd90f091297e223f2df002110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31309b49a53c7d1d117d4761bdd4a20afafafc053d67eb72bbbcc85716786ce9 0.600000000000 1401502 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": 943306, "vin": [ { "gen": { "height": 943296 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31309b49a53c7d1d117d4761bdd4a20afafafc053d67eb72bbbcc85716786ce9" } } ], "extra": [ 1, 25, 171, 89, 2, 28, 8, 94, 158, 78, 131, 30, 191, 103, 216, 83, 218, 219, 218, 44, 31, 227, 26, 205, 144, 240, 145, 41, 126, 34, 63, 45, 240, 2, 17, 0, 0, 0, 7, 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