Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3e85485be73d53e4cf4155f46e5408ef541d951605d46bff5c13bb0116c51bc

Tx prefix hash: 347ea3ba721235f57ab236251712dc9328f6ab927e6a770bc74c5be11145950c
Tx public key: a4b2f75e8517f9035d1bc116aa5746e63df6d8676027c1d15e9aeca2654c6205
Timestamp: 1745911696 Timestamp [UTC]: 2025-04-29 07:28:16 Age [y:d:h:m:s]: 01:016:11:57:41
Block: 1271867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262705 RingCT/type: yes/0
Extra: 01a4b2f75e8517f9035d1bc116aa5746e63df6d8676027c1d15e9aeca2654c620502110000000125a35a0f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 36a6fc7885aa8081ebe60ab2997915a9727fd9e20fdf748e63d28d40d331d107 0.000600000000 1759136 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": 1271877, "vin": [ { "gen": { "height": 1271867 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36a6fc7885aa8081ebe60ab2997915a9727fd9e20fdf748e63d28d40d331d107" } } ], "extra": [ 1, 164, 178, 247, 94, 133, 23, 249, 3, 93, 27, 193, 22, 170, 87, 70, 230, 61, 246, 216, 103, 96, 39, 193, 209, 94, 154, 236, 162, 101, 76, 98, 5, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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: