Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d978de6ef95e9a87f06b5175b940a04a0cd9c7c0e4a0a20df7420193a7281794

Tx prefix hash: a8f34c120a78a1a5f74808f16ab546df35190355f10f9b82e3282e8e06493174
Tx public key: 025b8c7b167553a5e8b1391a12d050faac045264beec26aa86537c51e2da194e
Timestamp: 1762372568 Timestamp [UTC]: 2025-11-05 19:56:08 Age [y:d:h:m:s]: 00:194:18:53:32
Block: 1405712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132609 RingCT/type: yes/0
Extra: 01025b8c7b167553a5e8b1391a12d050faac045264beec26aa86537c51e2da194e021100000005df5a247a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ad515b41c790109f857aa3ebb59bf1aefb6ad3fab5e0624be4f1e45b92840b1a 0.000600000000 1894093 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": 1405722, "vin": [ { "gen": { "height": 1405712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad515b41c790109f857aa3ebb59bf1aefb6ad3fab5e0624be4f1e45b92840b1a" } } ], "extra": [ 1, 2, 91, 140, 123, 22, 117, 83, 165, 232, 177, 57, 26, 18, 208, 80, 250, 172, 4, 82, 100, 190, 236, 38, 170, 134, 83, 124, 81, 226, 218, 25, 78, 2, 17, 0, 0, 0, 5, 223, 90, 36, 122, 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: