Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad61c93716eb537f8837befaa6d81090682ea064b9e34db994256d3885d7ee21

Tx prefix hash: 512435a5b8ae5a830b911e5cb0dd05615e0fb80f44f402ceb19471b5de035ecf
Tx public key: 079f63a3fcd6d3a3d4a43c345bebcdb6406f3d9a9217d8625cbf98f327d671dc
Timestamp: 1708005466 Timestamp [UTC]: 2024-02-15 13:57:46 Age [y:d:h:m:s]: 02:279:22:21:31
Block: 958112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 725284 RingCT/type: yes/0
Extra: 01079f63a3fcd6d3a3d4a43c345bebcdb6406f3d9a9217d8625cbf98f327d671dc0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e7736e1a7755ce6f86a5b88c9ec155544b144c5d3bfecda5b8eb644cd368a415 0.000600000000 1417465 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": 958122, "vin": [ { "gen": { "height": 958112 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7736e1a7755ce6f86a5b88c9ec155544b144c5d3bfecda5b8eb644cd368a415" } } ], "extra": [ 1, 7, 159, 99, 163, 252, 214, 211, 163, 212, 164, 60, 52, 91, 235, 205, 182, 64, 111, 61, 154, 146, 23, 216, 98, 92, 191, 152, 243, 39, 214, 113, 220, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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: