Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf60d34a2a226d1eec3d24bde541cbdfad78930c2bd6f345b16a325f6e99f13b

Tx prefix hash: a87288797b8a3dd43cb9823c4502fd792ab2be60ec5bb7ca0608d28c13062ae5
Tx public key: 7f7646fd84dfb028484d6d121258f07037644bcfecb56a24ff874c7cb3628d68
Timestamp: 1688314298 Timestamp [UTC]: 2023-07-02 16:11:38 Age [y:d:h:m:s]: 03:142:22:45:49
Block: 795133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 888351 RingCT/type: yes/0
Extra: 017f7646fd84dfb028484d6d121258f07037644bcfecb56a24ff874c7cb3628d6802110000000133af99f4000000000000000000

1 output(s) for total of 0.001423761154 xmr

stealth address amount amount idx tag
00: 271c65c3a631e9e8f7b602160c5e28de202478259b489c2cf7095146a727af42 0.001423761154 1245918 of 0 -

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": 795143, "vin": [ { "gen": { "height": 795133 } } ], "vout": [ { "amount": 1423761154, "target": { "key": "271c65c3a631e9e8f7b602160c5e28de202478259b489c2cf7095146a727af42" } } ], "extra": [ 1, 127, 118, 70, 253, 132, 223, 176, 40, 72, 77, 109, 18, 18, 88, 240, 112, 55, 100, 75, 207, 236, 181, 106, 36, 255, 135, 76, 124, 179, 98, 141, 104, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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: