Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48aedcd931358d6593bda074eaf539bd59dbeb25ac26639c30ce1c10c53a1c9e

Tx prefix hash: 79344fc0fd0255dc52248d90b8d37eebe1e99d2b7e474e4aa4437be9c13fadbb
Tx public key: 1ebb3896138282c99570ba7119fe25276ed86e7a9c0b0c37e3489c546c0ff66e
Timestamp: 1745440107 Timestamp [UTC]: 2025-04-23 20:28:27 Age [y:d:h:m:s]: 01:210:20:23:18
Block: 1267950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 414885 RingCT/type: yes/0
Extra: 011ebb3896138282c99570ba7119fe25276ed86e7a9c0b0c37e3489c546c0ff66e021100000003dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8275316b370522f3b504835f668262f656c45f8aa41c081bcea5dde4f1ed79b0 0.000600000000 1755179 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": 1267960, "vin": [ { "gen": { "height": 1267950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8275316b370522f3b504835f668262f656c45f8aa41c081bcea5dde4f1ed79b0" } } ], "extra": [ 1, 30, 187, 56, 150, 19, 130, 130, 201, 149, 112, 186, 113, 25, 254, 37, 39, 110, 216, 110, 122, 156, 11, 12, 55, 227, 72, 156, 84, 108, 15, 246, 110, 2, 17, 0, 0, 0, 3, 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: