Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aed57694d2b07eeb3a7e37bf2c7abc9233dc8d0599524b1b3203b165916c2b60

Tx prefix hash: 07c65d612a897b1cf1fdeb2e35ff343c8987f76581a7ebcd14218965e12f1363
Tx public key: 4f1887847d69a8e50b2aaee81d49b841c4399e05a6bf6f6c10e992b9f7211a80
Timestamp: 1774058866 Timestamp [UTC]: 2026-03-21 02:07:46 Age [y:d:h:m:s]: 00:239:12:48:37
Block: 1502320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176645 RingCT/type: yes/0
Extra: 014f1887847d69a8e50b2aaee81d49b841c4399e05a6bf6f6c10e992b9f7211a80021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 44ad7029b07697df3747cff260e4fda37e9f1efee42bb45dbc1650594d41cccb 0.000600000000 1992018 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": 1502330, "vin": [ { "gen": { "height": 1502320 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44ad7029b07697df3747cff260e4fda37e9f1efee42bb45dbc1650594d41cccb" } } ], "extra": [ 1, 79, 24, 135, 132, 125, 105, 168, 229, 11, 42, 174, 232, 29, 73, 184, 65, 196, 57, 158, 5, 166, 191, 111, 108, 16, 233, 146, 185, 247, 33, 26, 128, 2, 17, 0, 0, 0, 4, 228, 245, 25, 63, 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: