Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b60fc10d55684906897576c52185e78bdaf0c9c1648e450199e93d4c1c519c55

Tx prefix hash: e7cca008a76b05f05ec2a6e32d3202e219c7714b6f9ec7b8e59801225df04f5b
Tx public key: 855cca9534b9d38a4e60c9a9c0f1ca1034437717ee8bd1125a2e31ba65d5b1d6
Timestamp: 1729766945 Timestamp [UCT]: 2024-10-24 10:49:05 Age [y:d:h:m:s]: 00:192:17:47:18
Block: 1138489 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137567 RingCT/type: yes/0
Extra: 01855cca9534b9d38a4e60c9a9c0f1ca1034437717ee8bd1125a2e31ba65d5b1d60211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4313cff7beff7567e14fe48a5c32528c6ac0414fb7da7a3fed8efaff75badbc4 0.600000000000 1622170 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": 1138499, "vin": [ { "gen": { "height": 1138489 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4313cff7beff7567e14fe48a5c32528c6ac0414fb7da7a3fed8efaff75badbc4" } } ], "extra": [ 1, 133, 92, 202, 149, 52, 185, 211, 138, 78, 96, 201, 169, 192, 241, 202, 16, 52, 67, 119, 23, 238, 139, 209, 18, 90, 46, 49, 186, 101, 213, 177, 214, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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