Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9dc2cb02228847b76f6402a5f794476aa008e75f185c74db9ade9c0915ab3a7

Tx prefix hash: 4b82740b6cefb5f0e2372545094df23b996d6c2dcda2c1f001f919394f26efb1
Tx public key: e699c5271114d4de5a58382cf05859e9b5b05147a8440d8921f45ab5efe6fb3b
Timestamp: 1744573566 Timestamp [UTC]: 2025-04-13 19:46:06 Age [y:d:h:m:s]: 01:219:10:19:53
Block: 1260781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 420907 RingCT/type: yes/0
Extra: 01e699c5271114d4de5a58382cf05859e9b5b05147a8440d8921f45ab5efe6fb3b0211000000066c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e2961c104a8b32fc6c4a3f1ebc8d0c2abfacbe3c2d12a4aeea54d96772d64715 0.000600000000 1747942 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": 1260791, "vin": [ { "gen": { "height": 1260781 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2961c104a8b32fc6c4a3f1ebc8d0c2abfacbe3c2d12a4aeea54d96772d64715" } } ], "extra": [ 1, 230, 153, 197, 39, 17, 20, 212, 222, 90, 88, 56, 44, 240, 88, 89, 233, 181, 176, 81, 71, 168, 68, 13, 137, 33, 244, 90, 181, 239, 230, 251, 59, 2, 17, 0, 0, 0, 6, 108, 152, 170, 61, 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: