Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1b5a9bd2f3c9cd997322b0ec9519708aa3f2c0304a78fc63708bd10458b1bf9

Tx prefix hash: 2b938a20b26e22ebd7ed2969ad460b3f62cdcfa9c29fd2f1b3b28e7138364ccb
Tx public key: 1adf3abefb28b0d691e80a9056768f20e5cf034740ea00a1d60bd9d2c8ca6484
Timestamp: 1742320967 Timestamp [UTC]: 2025-03-18 18:02:47 Age [y:d:h:m:s]: 01:055:19:27:24
Block: 1242146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290725 RingCT/type: yes/0
Extra: 011adf3abefb28b0d691e80a9056768f20e5cf034740ea00a1d60bd9d2c8ca648402110000000c1f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3015a72e9b47b88052ef655b68593cff503becd0cf39e000e28f60afcea6e4f9 0.000600000000 1729119 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": 1242156, "vin": [ { "gen": { "height": 1242146 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3015a72e9b47b88052ef655b68593cff503becd0cf39e000e28f60afcea6e4f9" } } ], "extra": [ 1, 26, 223, 58, 190, 251, 40, 176, 214, 145, 232, 10, 144, 86, 118, 143, 32, 229, 207, 3, 71, 64, 234, 0, 161, 214, 11, 217, 210, 200, 202, 100, 132, 2, 17, 0, 0, 0, 12, 31, 10, 83, 235, 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: