Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96d842f986fd89cbaa0a4b968e8205cbd8e8b6a6901a1ad6e6771395294fd7d1

Tx prefix hash: 9574150e1b81e82bd3c71f3b9952ee51c28108e3241b88823dec0082315d59f9
Tx public key: ebe4ef6f36c4b58196d981cd8da0c082b15e5f42a27f6905de97e51b75aef825
Timestamp: 1744226135 Timestamp [UTC]: 2025-04-09 19:15:35 Age [y:d:h:m:s]: 01:164:04:32:39
Block: 1257891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 382090 RingCT/type: yes/0
Extra: 01ebe4ef6f36c4b58196d981cd8da0c082b15e5f42a27f6905de97e51b75aef8250211000000036c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 77c3355e16ef3fc374d4333f93bdbbbea8f68b1ccf1e4af2ab9794aaac408052 0.000600000000 1745022 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": 1257901, "vin": [ { "gen": { "height": 1257891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77c3355e16ef3fc374d4333f93bdbbbea8f68b1ccf1e4af2ab9794aaac408052" } } ], "extra": [ 1, 235, 228, 239, 111, 54, 196, 181, 129, 150, 217, 129, 205, 141, 160, 192, 130, 177, 94, 95, 66, 162, 127, 105, 5, 222, 151, 229, 27, 117, 174, 248, 37, 2, 17, 0, 0, 0, 3, 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: