Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a42cec5dcdab796936bf54a5116e11dc1a987d70a70181ccb9a275f700de114

Tx prefix hash: 7f2196532df9f026b5d74b52f26edca38c3dd8109aa43ff42944a93f56c88ada
Tx public key: 51a255c5b1cee30199bfed999e42dff0f266de5f8b25acfaf843e5ea77aaa5a3
Timestamp: 1709079837 Timestamp [UTC]: 2024-02-28 00:23:57 Age [y:d:h:m:s]: 02:177:20:23:03
Block: 967031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 652437 RingCT/type: yes/0
Extra: 0151a255c5b1cee30199bfed999e42dff0f266de5f8b25acfaf843e5ea77aaa5a30211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 56136111ef97b77c36ef089e78934a66448d69db488a33ccea2424fbdec9b171 0.000600000000 1426802 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": 967041, "vin": [ { "gen": { "height": 967031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56136111ef97b77c36ef089e78934a66448d69db488a33ccea2424fbdec9b171" } } ], "extra": [ 1, 81, 162, 85, 197, 177, 206, 227, 1, 153, 191, 237, 153, 158, 66, 223, 240, 242, 102, 222, 95, 139, 37, 172, 250, 248, 67, 229, 234, 119, 170, 165, 163, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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: