Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd33ed44b301cc22dd3386cd365927e39fec12fcdc652a1bda2b7df9e4db6e29

Tx prefix hash: 06795515471af1cee5c1d6d340f840b17d46298c57881872db0a8cc26bbc6268
Tx public key: b69bb3691e1ea92b3140540cf16a47a14e2f0fd2c365dd51c431b8948a0dc1e0
Timestamp: 1773406129 Timestamp [UTC]: 2026-03-13 12:48:49 Age [y:d:h:m:s]: 00:248:17:05:35
Block: 1496933 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183250 RingCT/type: yes/0
Extra: 01b69bb3691e1ea92b3140540cf16a47a14e2f0fd2c365dd51c431b8948a0dc1e0021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bd4a51fca9a01ac7c74554e0caf15b831d6010b2c2ea034c6b73863c50a309a3 0.000600000000 1986565 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": 1496943, "vin": [ { "gen": { "height": 1496933 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd4a51fca9a01ac7c74554e0caf15b831d6010b2c2ea034c6b73863c50a309a3" } } ], "extra": [ 1, 182, 155, 179, 105, 30, 30, 169, 43, 49, 64, 84, 12, 241, 106, 71, 161, 78, 47, 15, 210, 195, 101, 221, 81, 196, 49, 184, 148, 138, 13, 193, 224, 2, 17, 0, 0, 0, 1, 228, 245, 25, 63, 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: