Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b59effcea2d63106196eb3ca5481344071a0d1e98657cd62ed485ec50893c07

Tx prefix hash: 7590f5f7aa7555078c60bfa95fdc6f048e81b5489cad72c3af5f0e4b09231812
Tx public key: 278d7aaf9513b1e7d28efa74384a836889a6a73b9ae34d0e337d0b38e3ab6f0d
Timestamp: 1753509442 Timestamp [UTC]: 2025-07-26 05:57:22 Age [y:d:h:m:s]: 01:114:20:36:32
Block: 1333594 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347223 RingCT/type: yes/0
Extra: 01278d7aaf9513b1e7d28efa74384a836889a6a73b9ae34d0e337d0b38e3ab6f0d021100000005ef221485000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 09fddbf35f3fab839531a0b4b05808f8066c6d95f9509efea86ef370f5b81422 0.000600000000 1821393 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": 1333604, "vin": [ { "gen": { "height": 1333594 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09fddbf35f3fab839531a0b4b05808f8066c6d95f9509efea86ef370f5b81422" } } ], "extra": [ 1, 39, 141, 122, 175, 149, 19, 177, 231, 210, 142, 250, 116, 56, 74, 131, 104, 137, 166, 167, 59, 154, 227, 77, 14, 51, 125, 11, 56, 227, 171, 111, 13, 2, 17, 0, 0, 0, 5, 239, 34, 20, 133, 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: