Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce5a1944ed5b5ccfb89e07745e6db19047682ae7be3bffa364e63a8a1f0723a1

Tx prefix hash: 684e39b94e112c5749fa184d26c9863c818961eaba1b184909295af8fed38d07
Tx public key: 9fdd6d32cc2714e80c44ed81f8c0f5d41ebfa422e78618eca229f38ab72458ea
Timestamp: 1721302804 Timestamp [UCT]: 2024-07-18 11:40:04 Age [y:d:h:m:s]: 00:129:06:12:39
Block: 1068373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92471 RingCT/type: yes/0
Extra: 019fdd6d32cc2714e80c44ed81f8c0f5d41ebfa422e78618eca229f38ab72458ea021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a738cae89b4f483c63f8db9ba1d5e7b7a4f9eff4465ea9d933a230022cbd4cf8 0.600000000000 1539450 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": 1068383, "vin": [ { "gen": { "height": 1068373 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a738cae89b4f483c63f8db9ba1d5e7b7a4f9eff4465ea9d933a230022cbd4cf8" } } ], "extra": [ 1, 159, 221, 109, 50, 204, 39, 20, 232, 12, 68, 237, 129, 248, 192, 245, 212, 30, 191, 164, 34, 231, 134, 24, 236, 162, 41, 243, 138, 183, 36, 88, 234, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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