Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3212c1c152fa705e0c9e2bdd0a643c33c91b23155e27f20932237a66a4aed98f

Tx prefix hash: 38c8fd4fbb8714b63b5035f912b5c2a72f61f810c42eca42e936089fe7a40afe
Tx public key: d741e1360728aae6d4db4d0f0fba466f491f4af817f1e7808281a8a78c9e9601
Timestamp: 1695775936 Timestamp [UCT]: 2023-09-27 00:52:16 Age [y:d:h:m:s]: 02:045:09:05:08
Block: 856929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 552078 RingCT/type: yes/0
Extra: 01d741e1360728aae6d4db4d0f0fba466f491f4af817f1e7808281a8a78c9e960102110000000133af99f4000000000000000000

1 output(s) for total of 0.888461353000 dcy

stealth address amount amount idx
00: dd30cbd7bb7b0635ec5cc1d6f3e58fcf84277375134e5eb15f598eec31afdc88 0.888461353000 1311027 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": 856939, "vin": [ { "gen": { "height": 856929 } } ], "vout": [ { "amount": 888461353, "target": { "key": "dd30cbd7bb7b0635ec5cc1d6f3e58fcf84277375134e5eb15f598eec31afdc88" } } ], "extra": [ 1, 215, 65, 225, 54, 7, 40, 170, 230, 212, 219, 77, 15, 15, 186, 70, 111, 73, 31, 74, 248, 23, 241, 231, 128, 130, 129, 168, 167, 140, 158, 150, 1, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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