Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e53565ec5178a35bd27493f959c6bb0e83fc8d1b5748555ddddcb6013c78cd09

Tx prefix hash: 93bb4040251642b9ff718bea6b3166a453776caa8150f8129f0354a0eee8d169
Tx public key: 30aad62e2dcd6af816aff14d19266ac235cd9f0f55bce6919f25ea49fb807517
Timestamp: 1736621880 Timestamp [UTC]: 2025-01-11 18:58:00 Age [y:d:h:m:s]: 01:313:10:08:46
Block: 1195215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 487967 RingCT/type: yes/0
Extra: 0130aad62e2dcd6af816aff14d19266ac235cd9f0f55bce6919f25ea49fb807517021100000001007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: dd8e0ccc2c0fe03c6933d5f8471fb380300e24b8714bab7692d281cd8a3af40a 0.000600000000 1681804 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": 1195225, "vin": [ { "gen": { "height": 1195215 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd8e0ccc2c0fe03c6933d5f8471fb380300e24b8714bab7692d281cd8a3af40a" } } ], "extra": [ 1, 48, 170, 214, 46, 45, 205, 106, 248, 22, 175, 241, 77, 25, 38, 106, 194, 53, 205, 159, 15, 85, 188, 230, 145, 159, 37, 234, 73, 251, 128, 117, 23, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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: