Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6cf80bd6448bc3b72d72f6f94606f1bc0ab491aa757ae3ea6e07964d9516f51

Tx prefix hash: c8c953b187134cbbd27acbab02b4639cf192db7fc3876c649979d128fe93b65c
Tx public key: 672d6116ae79759252ab718cd82b53faf47d1387113a0ccf7eeaaeb0429ebf67
Timestamp: 1577611533 Timestamp [UTC]: 2019-12-29 09:25:33 Age [y:d:h:m:s]: 06:240:13:37:29
Block: 34215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1586054 RingCT/type: yes/0
Extra: 01672d6116ae79759252ab718cd82b53faf47d1387113a0ccf7eeaaeb0429ebf67021100000011d81c26c0000000000000000000

1 output(s) for total of 0.472750892904 xmr

stealth address amount amount idx tag
00: b9ff842e87cf51296e2aaca4f283250add2156f75988c4b2a7452c72da489161 0.472750892904 57585 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": 34225, "vin": [ { "gen": { "height": 34215 } } ], "vout": [ { "amount": 472750892904, "target": { "key": "b9ff842e87cf51296e2aaca4f283250add2156f75988c4b2a7452c72da489161" } } ], "extra": [ 1, 103, 45, 97, 22, 174, 121, 117, 146, 82, 171, 113, 140, 216, 43, 83, 250, 244, 125, 19, 135, 17, 58, 12, 207, 126, 234, 174, 176, 66, 158, 191, 103, 2, 17, 0, 0, 0, 17, 216, 28, 38, 192, 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: