Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edb3e877864787fab06ac6142fcc5d4f4ff8a8bd29ddbcedfcc1632b2e499f9d

Tx prefix hash: f9495d9576d12ed9a51f0f3fd13bbf4d1d902f644b326e79dbabe3d80f0684c1
Tx public key: 66206548d5327225a184466c5907a34eadcae2dfd58b754102a5706bd234669d
Timestamp: 1757479431 Timestamp [UTC]: 2025-09-10 04:43:51 Age [y:d:h:m:s]: 00:259:07:42:46
Block: 1365195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179333 RingCT/type: yes/0
Extra: 0166206548d5327225a184466c5907a34eadcae2dfd58b754102a5706bd234669d021100000011ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 266550ee5e716e083608cde0b06572e06754292d6b759482407c19e5edf4fdff 0.000600000000 1853234 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": 1365205, "vin": [ { "gen": { "height": 1365195 } } ], "vout": [ { "amount": 600000000, "target": { "key": "266550ee5e716e083608cde0b06572e06754292d6b759482407c19e5edf4fdff" } } ], "extra": [ 1, 102, 32, 101, 72, 213, 50, 114, 37, 161, 132, 70, 108, 89, 7, 163, 78, 173, 202, 226, 223, 213, 139, 117, 65, 2, 165, 112, 107, 210, 52, 102, 157, 2, 17, 0, 0, 0, 17, 173, 121, 72, 208, 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: