Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0feb1c81daf01644b097bb1a065002afce51188136baa42cd012a5a6266eeb0e

Tx prefix hash: efca834aa3f89112922c27d2382a1bc9542e7dc057e255e6da3fd81c293a5cbe
Tx public key: 32397a17e43f4f3012f76c49abf5d93e9023f940de60f7abcb29be2b5ceef625
Timestamp: 1721081110 Timestamp [UCT]: 2024-07-15 22:05:10 Age [y:d:h:m:s]: 00:253:15:41:23
Block: 1066529 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181192 RingCT/type: yes/0
Extra: 0132397a17e43f4f3012f76c49abf5d93e9023f940de60f7abcb29be2b5ceef625021100000014e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a5974c82abffa11b1142134d18a713da4ac5883205cef1be43caa6d72bff381 0.600000000000 1537180 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": 1066539, "vin": [ { "gen": { "height": 1066529 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a5974c82abffa11b1142134d18a713da4ac5883205cef1be43caa6d72bff381" } } ], "extra": [ 1, 50, 57, 122, 23, 228, 63, 79, 48, 18, 247, 108, 73, 171, 245, 217, 62, 144, 35, 249, 64, 222, 96, 247, 171, 203, 41, 190, 43, 92, 238, 246, 37, 2, 17, 0, 0, 0, 20, 233, 20, 221, 21, 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