Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bc357d9d24c08bfa5d10119bafc1500e0d53c1a2d30a06260fa58d802a9bc77

Tx prefix hash: 68b83ffa1f58cc37e0a104a8bb7d9e00e82d73acfe14711689c8f7c3838572fe
Tx public key: 8caa1adea2afa86e171313229cf507e7cd04383ec7f6ec83c1b9a75f8ffa629f
Timestamp: 1699841122 Timestamp [UCT]: 2023-11-13 02:05:22 Age [y:d:h:m:s]: 02:007:21:37:18
Block: 890442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 525417 RingCT/type: yes/0
Extra: 018caa1adea2afa86e171313229cf507e7cd04383ec7f6ec83c1b9a75f8ffa629f021100000004faf35c9c000000000000000000

1 output(s) for total of 0.688011997000 dcy

stealth address amount amount idx
00: 616f23b0afdb8a003ec6cb384e1fcd1d96aae98a706a9ab7f0a4ee8712661939 0.688011997000 1346465 of 0

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": 890452, "vin": [ { "gen": { "height": 890442 } } ], "vout": [ { "amount": 688011997, "target": { "key": "616f23b0afdb8a003ec6cb384e1fcd1d96aae98a706a9ab7f0a4ee8712661939" } } ], "extra": [ 1, 140, 170, 26, 222, 162, 175, 168, 110, 23, 19, 19, 34, 156, 245, 7, 231, 205, 4, 56, 62, 199, 246, 236, 131, 193, 185, 167, 95, 143, 250, 98, 159, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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