Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb4a202ecf9a3f87b6b1268617078c642a4614d533dec7550cc45d4722d146b4

Tx prefix hash: e412398161feb1cc376a98c234442f810de96d55ce44b0fbe3f699a6a75a77c9
Tx public key: bda2658d916e5a898b8fd214e825592cb8d791cec889b1d032db382a45855b2c
Timestamp: 1646078449 Timestamp [UCT]: 2022-02-28 20:00:49 Age [y:d:h:m:s]: 03:055:22:27:03
Block: 448569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 820038 RingCT/type: yes/0
Extra: 01bda2658d916e5a898b8fd214e825592cb8d791cec889b1d032db382a45855b2c021100000009bf7ee4e7000000000000000000

1 output(s) for total of 20.031108070000 dcy

stealth address amount amount idx
00: 83c3e136cc5ecec129f5db3c188863edee1c2ea5a60b47cb68f2fcfb047a352b 20.031108070000 862976 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": 448579, "vin": [ { "gen": { "height": 448569 } } ], "vout": [ { "amount": 20031108070, "target": { "key": "83c3e136cc5ecec129f5db3c188863edee1c2ea5a60b47cb68f2fcfb047a352b" } } ], "extra": [ 1, 189, 162, 101, 141, 145, 110, 90, 137, 139, 143, 210, 20, 232, 37, 89, 44, 184, 215, 145, 206, 200, 137, 177, 208, 50, 219, 56, 42, 69, 133, 91, 44, 2, 17, 0, 0, 0, 9, 191, 126, 228, 231, 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