Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7da00f964d0db2e34ca2b7e7db2467252ca951a6b40adee34ac18b524ccfced0

Tx prefix hash: 91b6ac7350c3678e8c0a4f3ea6f91a2c13652b53f0112746336b5ba132452fa8
Tx public key: 767e1b19a940c67b33ae8e6a0d36eca6dffd0b3700ff27b5e0742ae5f9f69c09
Timestamp: 1757198409 Timestamp [UTC]: 2025-09-06 22:40:09 Age [y:d:h:m:s]: 01:074:10:29:59
Block: 1362934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319631 RingCT/type: yes/0
Extra: 01767e1b19a940c67b33ae8e6a0d36eca6dffd0b3700ff27b5e0742ae5f9f69c09021100000007b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 219c20c8026b28cd3d8a10a94d00ac5dcc33cbc7277820ec4b1453005dcbac8c 0.000600000000 1850973 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 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": 1362944, "vin": [ { "gen": { "height": 1362934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "219c20c8026b28cd3d8a10a94d00ac5dcc33cbc7277820ec4b1453005dcbac8c" } } ], "extra": [ 1, 118, 126, 27, 25, 169, 64, 198, 123, 51, 174, 142, 106, 13, 54, 236, 166, 223, 253, 11, 55, 0, 255, 39, 181, 224, 116, 42, 229, 249, 246, 156, 9, 2, 17, 0, 0, 0, 7, 178, 247, 132, 196, 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: