Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f5ed863a40d76d5a0653f7c748dc1a8724e01dac118c1187906ec149e947a2c

Tx prefix hash: 5f4197338f11781156d2663a9b66b4a65dfe04ab0e094bcd645289cc425f4480
Tx public key: 78a2bf2af776c454de76968015e9cc92add263eb5148856452ba1f22ed66c753
Timestamp: 1577371287 Timestamp [UTC]: 2019-12-26 14:41:27 Age [y:d:h:m:s]: 06:269:17:16:34
Block: 32248 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1607239 RingCT/type: yes/0
Extra: 0178a2bf2af776c454de76968015e9cc92add263eb5148856452ba1f22ed66c7530211000000028a2ee0d9000000000000000000

1 output(s) for total of 0.479899003588 xmr

stealth address amount amount idx tag
00: 44e27f9e67af3f8c3d1297a4934f5a2a481cc9973a4ec0cf1fc073d25ced3806 0.479899003588 53598 of 0 -

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 dinastycoin-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": 32258, "vin": [ { "gen": { "height": 32248 } } ], "vout": [ { "amount": 479899003588, "target": { "key": "44e27f9e67af3f8c3d1297a4934f5a2a481cc9973a4ec0cf1fc073d25ced3806" } } ], "extra": [ 1, 120, 162, 191, 42, 247, 118, 196, 84, 222, 118, 150, 128, 21, 233, 204, 146, 173, 210, 99, 235, 81, 72, 133, 100, 82, 186, 31, 34, 237, 102, 199, 83, 2, 17, 0, 0, 0, 2, 138, 46, 224, 217, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: