Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c129fbf45cfae92b5cc1f79690d984a6f42a5247dbdbf83bbe4e75cc6b787ba

Tx prefix hash: 4f4fc145f935d9cad085e8e93c86d9cd3ef46b651cfd77b63a6e927aa341e668
Tx public key: 710bccea470ea61c76a8ea88f1108d3fcc6f6e262e6d0e0b2d5902d23f3ae960
Timestamp: 1725573917 Timestamp [UCT]: 2024-09-05 22:05:17 Age [y:d:h:m:s]: 00:212:23:43:46
Block: 1103771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152046 RingCT/type: yes/0
Extra: 01710bccea470ea61c76a8ea88f1108d3fcc6f6e262e6d0e0b2d5902d23f3ae960021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c162302eac30fcd3128c6db41699e718840a8015cf5e22156854022027ba1ad2 0.600000000000 1580728 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 dinasty-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": 1103781, "vin": [ { "gen": { "height": 1103771 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c162302eac30fcd3128c6db41699e718840a8015cf5e22156854022027ba1ad2" } } ], "extra": [ 1, 113, 11, 204, 234, 71, 14, 166, 28, 118, 168, 234, 136, 241, 16, 141, 63, 204, 111, 110, 38, 46, 109, 14, 11, 45, 89, 2, 210, 63, 58, 233, 96, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8