Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddedce0aafae64da10d9b12bc328783046f315df60fd8cc5af3e5451f6f88c99

Tx prefix hash: be35a5dbd067622225a72f5adaacb774298b4f0606e3a462196873b976129b7d
Tx public key: 495536540e66c3556b93e1b7ccfcc1da526e8190649d8415c9116cc2b3ea0e7c
Timestamp: 1704532274 Timestamp [UCT]: 2024-01-06 09:11:14 Age [y:d:h:m:s]: 01:331:05:33:52
Block: 929299 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495601 RingCT/type: yes/0
Extra: 01495536540e66c3556b93e1b7ccfcc1da526e8190649d8415c9116cc2b3ea0e7c0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c97fa054f463b6e027320ef0c0c7c168e5eb57fca05d239e741f893527b7104 0.600000000000 1387171 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": 929309, "vin": [ { "gen": { "height": 929299 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c97fa054f463b6e027320ef0c0c7c168e5eb57fca05d239e741f893527b7104" } } ], "extra": [ 1, 73, 85, 54, 84, 14, 102, 195, 85, 107, 147, 225, 183, 204, 252, 193, 218, 82, 110, 129, 144, 100, 157, 132, 21, 201, 17, 108, 194, 179, 234, 14, 124, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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