Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c563cb41f30de41445bd5de11d85d8ef875126f8188c54cb3d66bf327e08cddd

Tx prefix hash: 2a5209495a91f3c912f17213115a2b63ba243efac92cfef08e8771ba764bd339
Tx public key: e565c382c1b2e7cce557032f001a727f0384309438248c73de5aae7451e315e8
Timestamp: 1722482800 Timestamp [UTC]: 2024-08-01 03:26:40 Age [y:d:h:m:s]: 01:291:04:08:07
Block: 1078136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 459971 RingCT/type: yes/0
Extra: 01e565c382c1b2e7cce557032f001a727f0384309438248c73de5aae7451e315e802110000000991e13c04000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 873baf980335442f4719d5de460f34343bc001163d8d0d23bd6a0842df225530 0.000600000000 1550703 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": 1078146, "vin": [ { "gen": { "height": 1078136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "873baf980335442f4719d5de460f34343bc001163d8d0d23bd6a0842df225530" } } ], "extra": [ 1, 229, 101, 195, 130, 193, 178, 231, 204, 229, 87, 3, 47, 0, 26, 114, 127, 3, 132, 48, 148, 56, 36, 140, 115, 222, 90, 174, 116, 81, 227, 21, 232, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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: