Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53e87f32ae2dd64ade7c68c632dbe88e0390e945198d1d758d89ba28a0f6cd8f

Tx prefix hash: f42c309005db86471e584efffdf2b50f143c6e9774a28dd494d192069efe3a75
Tx public key: 16d8012c6e1839dadd655f9798e09d137f9d8cd4e17a58a814808cdc040a19f8
Timestamp: 1738966697 Timestamp [UTC]: 2025-02-07 22:18:17 Age [y:d:h:m:s]: 01:283:01:50:50
Block: 1214369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 466374 RingCT/type: yes/0
Extra: 0116d8012c6e1839dadd655f9798e09d137f9d8cd4e17a58a814808cdc040a19f8021100000001007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: dbb1be4cf20d675af1cf27b7f44f59ee2c96d61eafbbac920cb27aab7991beab 0.000600000000 1701160 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": 1214379, "vin": [ { "gen": { "height": 1214369 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbb1be4cf20d675af1cf27b7f44f59ee2c96d61eafbbac920cb27aab7991beab" } } ], "extra": [ 1, 22, 216, 1, 44, 110, 24, 57, 218, 221, 101, 95, 151, 152, 224, 157, 19, 127, 157, 140, 212, 225, 122, 88, 168, 20, 128, 140, 220, 4, 10, 25, 248, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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: