Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56fc8b244312ed962b02d167e89c86b320c9f8e2db4a5bee5e76fb1f70d3fbf1

Tx prefix hash: bdad24cb9b15e0931ce479d34cf4a74c1d0b8b6451441cdfe555dd647393c835
Tx public key: 6b69484c9f2723526234400b8ed8569ff8608a6723388cb4e5aea9a13ea8fc0b
Timestamp: 1756719226 Timestamp [UTC]: 2025-09-01 09:33:46 Age [y:d:h:m:s]: 01:074:23:14:44
Block: 1358988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319789 RingCT/type: yes/0
Extra: 016b69484c9f2723526234400b8ed8569ff8608a6723388cb4e5aea9a13ea8fc0b021100000004b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3c91428c86ca293dd71cd7283916c98a07a4d075238bad96e20fa4fa94e58d2b 0.000600000000 1847001 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": 1358998, "vin": [ { "gen": { "height": 1358988 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c91428c86ca293dd71cd7283916c98a07a4d075238bad96e20fa4fa94e58d2b" } } ], "extra": [ 1, 107, 105, 72, 76, 159, 39, 35, 82, 98, 52, 64, 11, 142, 216, 86, 159, 248, 96, 138, 103, 35, 56, 140, 180, 229, 174, 169, 161, 62, 168, 252, 11, 2, 17, 0, 0, 0, 4, 178, 247, 132, 196, 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: