Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 825cc091ebf248fe9fa102f1ccb7b24c5d9d3603d13d004e02fc096ed9c1cd63

Tx prefix hash: 18b986597144e2b3f33451220b64145f61438811274e1d353cc8087b82495f88
Tx public key: 706d17e2dacb55bec729ffee7c43fa339194c4ce081ae05f0274220c1340a1cb
Timestamp: 1743602472 Timestamp [UTC]: 2025-04-02 14:01:12 Age [y:d:h:m:s]: 01:230:10:34:34
Block: 1252746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 428762 RingCT/type: yes/0
Extra: 01706d17e2dacb55bec729ffee7c43fa339194c4ce081ae05f0274220c1340a1cb0211000000054060f6d2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 614b00303fe322982303ceace8ac5fd244548de5d4bb6bd4b2be5165a0e3c8e0 0.000600000000 1739827 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": 1252756, "vin": [ { "gen": { "height": 1252746 } } ], "vout": [ { "amount": 600000000, "target": { "key": "614b00303fe322982303ceace8ac5fd244548de5d4bb6bd4b2be5165a0e3c8e0" } } ], "extra": [ 1, 112, 109, 23, 226, 218, 203, 85, 190, 199, 41, 255, 238, 124, 67, 250, 51, 145, 148, 196, 206, 8, 26, 224, 95, 2, 116, 34, 12, 19, 64, 161, 203, 2, 17, 0, 0, 0, 5, 64, 96, 246, 210, 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: