Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cc512bcb43cc466691e1f0008be3c01feb6b16c9b1fef3798df946d1ac64cb6

Tx prefix hash: d29d6ef11648452f328c47c9316b0fa8e58f1fe378593b76dd38b086f6107352
Tx public key: dd1ce037f90a8a59c2f5fc106e13b3d9b5e22313672d1a8d1ca0d6a3df8fd168
Timestamp: 1735455165 Timestamp [UCT]: 2024-12-29 06:52:45 Age [y:d:h:m:s]: 00:117:20:03:19
Block: 1185552 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84019 RingCT/type: yes/0
Extra: 01dd1ce037f90a8a59c2f5fc106e13b3d9b5e22313672d1a8d1ca0d6a3df8fd168021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16bf16b9b520286ff6b140c549aa009635d30b367052f56e67c08275413f4a18 0.600000000000 1672025 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": 1185562, "vin": [ { "gen": { "height": 1185552 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16bf16b9b520286ff6b140c549aa009635d30b367052f56e67c08275413f4a18" } } ], "extra": [ 1, 221, 28, 224, 55, 249, 10, 138, 89, 194, 245, 252, 16, 110, 19, 179, 217, 181, 226, 35, 19, 103, 45, 26, 141, 28, 160, 214, 163, 223, 143, 209, 104, 2, 17, 0, 0, 0, 2, 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