Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64f9e36718f6a99dc71a29d85ebef375f9c026114ff405c3d1a184d405cd4a64

Tx prefix hash: d0004375c91e49b19eba689a2db79793b3f23e4ed3ebea6073cae39212b71f7d
Tx public key: aec303d8493f7b1b1acfee62345ee3ef843297a5dfd4c005df4d9de20ffcc6ef
Timestamp: 1744181466 Timestamp [UTC]: 2025-04-09 06:51:06 Age [y:d:h:m:s]: 01:220:14:19:37
Block: 1257528 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 421637 RingCT/type: yes/0
Extra: 01aec303d8493f7b1b1acfee62345ee3ef843297a5dfd4c005df4d9de20ffcc6ef021100000009dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8c19a6895dd8c19368945392f4eaa641af6147a144b80b1b13c016102d75d4f7 0.000600000000 1744653 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": 1257538, "vin": [ { "gen": { "height": 1257528 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c19a6895dd8c19368945392f4eaa641af6147a144b80b1b13c016102d75d4f7" } } ], "extra": [ 1, 174, 195, 3, 216, 73, 63, 123, 27, 26, 207, 238, 98, 52, 94, 227, 239, 132, 50, 151, 165, 223, 212, 192, 5, 223, 77, 157, 226, 15, 252, 198, 239, 2, 17, 0, 0, 0, 9, 219, 181, 113, 193, 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: