Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46a75498ac33820ae5bf3827a2a8f81b6d2fa07f78c2d0f1a9fdadca499c573e

Tx prefix hash: 44a8aab2a1219ffc9a4304cf8214878498b79c45e5b6f7b7e671aeab32e980a1
Tx public key: de25f9cdfd24ee63970f5aef30074e6913f0f974ae1060fb4b29d6e5484bac26
Timestamp: 1729307882 Timestamp [UCT]: 2024-10-19 03:18:02 Age [y:d:h:m:s]: 00:177:10:27:02
Block: 1134716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126598 RingCT/type: yes/0
Extra: 01de25f9cdfd24ee63970f5aef30074e6913f0f974ae1060fb4b29d6e5484bac2602110000000e1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19ed058133ca393731c9da2537f325699ed6a218a7c43cd836dea64761bae734 0.600000000000 1618043 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": 1134726, "vin": [ { "gen": { "height": 1134716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19ed058133ca393731c9da2537f325699ed6a218a7c43cd836dea64761bae734" } } ], "extra": [ 1, 222, 37, 249, 205, 253, 36, 238, 99, 151, 15, 90, 239, 48, 7, 78, 105, 19, 240, 249, 116, 174, 16, 96, 251, 75, 41, 214, 229, 72, 75, 172, 38, 2, 17, 0, 0, 0, 14, 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