Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddd4a985940bcb5f1b189cf277ff9d11d946a01ae7e0a84dc1f2dfa31868fe0b

Tx prefix hash: e523a4fbdad3e67a73d172c93c38ee82f87591b26e4a6189663245bedbd888a5
Tx public key: 0b410b9eaa4794049ebd89ccda2174b8b20f76b6dc7f2e1f592a07772a1eda90
Timestamp: 1682857528 Timestamp [UCT]: 2023-04-30 12:25:28 Age [y:d:h:m:s]: 01:347:04:53:30
Block: 749877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 509392 RingCT/type: yes/0
Extra: 010b410b9eaa4794049ebd89ccda2174b8b20f76b6dc7f2e1f592a07772a1eda90021100000006faf35c9c000000000000000000

1 output(s) for total of 2.010695998000 dcy

stealth address amount amount idx
00: cedc8f940c853fbc94180c5e509a46e908c82ef39501cfc8e0bc54866c43dd6c 2.010695998000 1197896 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": 749887, "vin": [ { "gen": { "height": 749877 } } ], "vout": [ { "amount": 2010695998, "target": { "key": "cedc8f940c853fbc94180c5e509a46e908c82ef39501cfc8e0bc54866c43dd6c" } } ], "extra": [ 1, 11, 65, 11, 158, 170, 71, 148, 4, 158, 189, 137, 204, 218, 33, 116, 184, 178, 15, 118, 182, 220, 127, 46, 31, 89, 42, 7, 119, 42, 30, 218, 144, 2, 17, 0, 0, 0, 6, 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