Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecc489243ff02d992f93e50f602f7c3764ffb2e867a785fef336902da9a4e659

Tx prefix hash: 59cf0ac4655fa56eaf67d78b27706b9aab2e5918c099a0c26374af516cd716b5
Tx public key: 9494c7105231cd8c46dae72fb5adcab7d3a472c59f9ae0cd29432894c26c9c59
Timestamp: 1733531809 Timestamp [UCT]: 2024-12-07 00:36:49 Age [y:d:h:m:s]: 00:110:01:41:10
Block: 1169635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78448 RingCT/type: yes/0
Extra: 019494c7105231cd8c46dae72fb5adcab7d3a472c59f9ae0cd29432894c26c9c59021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf3cf4ee794c7bd94867e92afe6eb78622e62360e375424a1520e3d1e41fd437 0.600000000000 1655356 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": 1169645, "vin": [ { "gen": { "height": 1169635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf3cf4ee794c7bd94867e92afe6eb78622e62360e375424a1520e3d1e41fd437" } } ], "extra": [ 1, 148, 148, 199, 16, 82, 49, 205, 140, 70, 218, 231, 47, 181, 173, 202, 183, 211, 164, 114, 197, 159, 154, 224, 205, 41, 67, 40, 148, 194, 108, 156, 89, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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