Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dbf3dc13fc4c45265cc865d630bc67d5f89b6216667dadc669e9b85567cdce8

Tx prefix hash: c23d0c47710733d5d63b22ce03a79d8624377344ccfc0f9a189afc53d0c01d26
Tx public key: effc0ce14dc3426f747a2e371d01d3a429ed5420904fd7799646a83e1ca9db23
Timestamp: 1774729456 Timestamp [UTC]: 2026-03-28 20:24:16 Age [y:d:h:m:s]: 00:234:15:01:48
Block: 1507877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173223 RingCT/type: yes/0
Extra: 01effc0ce14dc3426f747a2e371d01d3a429ed5420904fd7799646a83e1ca9db23021100000005f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1681722c0db8ac295c3530c03cdfbb65c5baf319f9eca82bdefd5f3b40d5f54b 0.000600000000 1997629 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": 1507887, "vin": [ { "gen": { "height": 1507877 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1681722c0db8ac295c3530c03cdfbb65c5baf319f9eca82bdefd5f3b40d5f54b" } } ], "extra": [ 1, 239, 252, 12, 225, 77, 195, 66, 111, 116, 122, 46, 55, 29, 1, 211, 164, 41, 237, 84, 32, 144, 79, 215, 121, 150, 70, 168, 62, 28, 169, 219, 35, 2, 17, 0, 0, 0, 5, 241, 136, 200, 168, 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: