Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7070d2b01f5724caede2b862eae70cd9b894c70e67ad663c392958ceafe03af

Tx prefix hash: 0983d0a4e15e8cba91ebdd249e861f5d9c87365e761a2efd676105b59dc5a954
Tx public key: 1d5d5e9fefe2c18d8c8ce71e83a9b1319b5a2318785a856eab121266de2a1ad5
Timestamp: 1783848020 Timestamp [UTC]: 2026-07-12 09:20:20 Age [y:d:h:m:s]: 00:131:09:47:32
Block: 1580502 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 102377 RingCT/type: yes/0
Extra: 011d5d5e9fefe2c18d8c8ce71e83a9b1319b5a2318785a856eab121266de2a1ad5020875749e06922cdd40

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d3f6a57dcc788cdd907bb2c34d7d049ac5687b4687a17535513504bd3824e377 0.000600000000 2070494 of 15 <d2>

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": 1580512, "vin": [ { "gen": { "height": 1580502 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "d3f6a57dcc788cdd907bb2c34d7d049ac5687b4687a17535513504bd3824e377", "view_tag": "d2" } } } ], "extra": [ 1, 29, 93, 94, 159, 239, 226, 193, 141, 140, 140, 231, 30, 131, 169, 177, 49, 155, 90, 35, 24, 120, 90, 133, 110, 171, 18, 18, 102, 222, 42, 26, 213, 2, 8, 117, 116, 158, 6, 146, 44, 221, 64 ], "rct_signatures": { "type": 0 } }


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