Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f2918e2947d346fab431bf374c8b52ee9b94c8e9ca0b1cbd20ff836bcf7d996

Tx prefix hash: f58590a6c8baaf416246bca2cf457154fc12ee59d7a22a1227696ea68e35aed2
Tx public key: 7bf6ffe20fda92e983a1c02677b111f9c137c314819da3f68eca71bd006a625e
Timestamp: 1774790276 Timestamp [UTC]: 2026-03-29 13:17:56 Age [y:d:h:m:s]: 00:229:00:33:59
Block: 1508393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169040 RingCT/type: yes/0
Extra: 017bf6ffe20fda92e983a1c02677b111f9c137c314819da3f68eca71bd006a625e021100000009f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 649fee57622b104958cd8cce97ae14af07c236de3c5c6d15ea71295f6c1e435c 0.000600000000 1998145 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": 1508403, "vin": [ { "gen": { "height": 1508393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "649fee57622b104958cd8cce97ae14af07c236de3c5c6d15ea71295f6c1e435c" } } ], "extra": [ 1, 123, 246, 255, 226, 15, 218, 146, 233, 131, 161, 192, 38, 119, 177, 17, 249, 193, 55, 195, 20, 129, 157, 163, 246, 142, 202, 113, 189, 0, 106, 98, 94, 2, 17, 0, 0, 0, 9, 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: