Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 008930f217bd117ef84054b089b4e3ed7ca3957679bd2602e0c533e92a0c656a

Tx prefix hash: d92c5385ad0ea231aa4c83e43c3496378881c30b4458b38a420b1a907e3c2d54
Tx public key: 39755dcc52467deceb9ee2d003d8760abd8532ee0d138010e6d08d9296904de4
Timestamp: 1747549701 Timestamp [UTC]: 2025-05-18 06:28:21 Age [y:d:h:m:s]: 00:364:07:06:51
Block: 1285420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250490 RingCT/type: yes/0
Extra: 0139755dcc52467deceb9ee2d003d8760abd8532ee0d138010e6d08d9296904de40211000000079f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e3c81d2fe260b8bd15167e6ea6af4e3c528e1292f52ec134c0f8b49f3e64f860 0.000600000000 1772885 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": 1285430, "vin": [ { "gen": { "height": 1285420 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3c81d2fe260b8bd15167e6ea6af4e3c528e1292f52ec134c0f8b49f3e64f860" } } ], "extra": [ 1, 57, 117, 93, 204, 82, 70, 125, 236, 235, 158, 226, 208, 3, 216, 118, 10, 189, 133, 50, 238, 13, 19, 128, 16, 230, 208, 141, 146, 150, 144, 77, 228, 2, 17, 0, 0, 0, 7, 159, 159, 230, 140, 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: