Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fff47fe4e9d0ada26c876e3f38ca0fd083086261a1f82a1e5649c9726079f88

Tx prefix hash: 49273db60f80535752a1161c9e7a9024083e4353f9915196e4043a693bf4d14f
Tx public key: 7ad7b6e960ee44bc826983c36103a72ec9b750b4b344c7d04e87e809cf5245e2
Timestamp: 1734427709 Timestamp [UCT]: 2024-12-17 09:28:29 Age [y:d:h:m:s]: 00:092:02:09:02
Block: 1177077 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65597 RingCT/type: yes/0
Extra: 017ad7b6e960ee44bc826983c36103a72ec9b750b4b344c7d04e87e809cf5245e20211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6e3391c6d83bb6f5d276dc6be5539d6c73e2d1fde624214163e1bb0f30bacd1 0.600000000000 1663440 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": 1177087, "vin": [ { "gen": { "height": 1177077 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6e3391c6d83bb6f5d276dc6be5539d6c73e2d1fde624214163e1bb0f30bacd1" } } ], "extra": [ 1, 122, 215, 182, 233, 96, 238, 68, 188, 130, 105, 131, 195, 97, 3, 167, 46, 201, 183, 80, 180, 179, 68, 199, 208, 78, 135, 232, 9, 207, 82, 69, 226, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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