Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e3c2824778764110e70d2af4dbc69f1ab8a1a8a37d07f919d0a219ced1b3487

Tx prefix hash: fd8151bea2ab723449bef1b5d87ce63135cf3e9ba021f57d9e8d690ce4a8657b
Tx public key: 74f3404f3c7faade0d31fe84535346cbf176b15b7f3ffafe293299e9e84321d7
Timestamp: 1749237505 Timestamp [UTC]: 2025-06-06 19:18:25 Age [y:d:h:m:s]: 00:342:20:35:18
Block: 1299398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235061 RingCT/type: yes/0
Extra: 0174f3404f3c7faade0d31fe84535346cbf176b15b7f3ffafe293299e9e84321d702110000000443846d66000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c52839a35f94fe2f7ec73fb369cba1eda302fc87f336a66a1afac23eaffba989 0.000600000000 1786935 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": 1299408, "vin": [ { "gen": { "height": 1299398 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c52839a35f94fe2f7ec73fb369cba1eda302fc87f336a66a1afac23eaffba989" } } ], "extra": [ 1, 116, 243, 64, 79, 60, 127, 170, 222, 13, 49, 254, 132, 83, 83, 70, 203, 241, 118, 177, 91, 127, 63, 250, 254, 41, 50, 153, 233, 232, 67, 33, 215, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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: