Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04d05631400a58e935481c1dbd8b650535edb537189a007ebb8517c303af63d3

Tx prefix hash: a6f4ddcf4c58111c607d7d1e03d13d61d9c155d5be0f543505abe78107e342c7
Tx public key: 97a44a0b6730ab4aa9299cb7ed426ebff9297d21941437c449fb29c0c9a4cf71
Timestamp: 1758305535 Timestamp [UTC]: 2025-09-19 18:12:15 Age [y:d:h:m:s]: 01:055:23:53:08
Block: 1372016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306295 RingCT/type: yes/0
Extra: 0197a44a0b6730ab4aa9299cb7ed426ebff9297d21941437c449fb29c0c9a4cf71021100000003b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ad76914ee231a19de0f72783f92803ee28388a2e7a2d8a80cca974e9e2279954 0.000600000000 1860101 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": 1372026, "vin": [ { "gen": { "height": 1372016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad76914ee231a19de0f72783f92803ee28388a2e7a2d8a80cca974e9e2279954" } } ], "extra": [ 1, 151, 164, 74, 11, 103, 48, 171, 74, 169, 41, 156, 183, 237, 66, 110, 191, 249, 41, 125, 33, 148, 20, 55, 196, 73, 251, 41, 192, 201, 164, 207, 113, 2, 17, 0, 0, 0, 3, 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: