Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c23555acf4ee4eb40c41cd41c7e086cf4b7139c9f123e4522fc76679d7b308d

Tx prefix hash: f7884ae2ce4781a4532c3e6ffe89462bdb45ac6264d119d7c0352295aeec6ee6
Tx public key: e85538137f2c17591f65061c51d1c95773094204e89292bcf0f1c75ddf42b112
Timestamp: 1718997654 Timestamp [UCT]: 2024-06-21 19:20:54 Age [y:d:h:m:s]: 00:328:02:38:37
Block: 1049219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234511 RingCT/type: yes/0
Extra: 01e85538137f2c17591f65061c51d1c95773094204e89292bcf0f1c75ddf42b11202110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a565676364fbeae0e3fa4e3d6f0d09e0ad291c8a1c5c8964e84efc0a4a854260 0.600000000000 1519316 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": 1049229, "vin": [ { "gen": { "height": 1049219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a565676364fbeae0e3fa4e3d6f0d09e0ad291c8a1c5c8964e84efc0a4a854260" } } ], "extra": [ 1, 232, 85, 56, 19, 127, 44, 23, 89, 31, 101, 6, 28, 81, 209, 201, 87, 115, 9, 66, 4, 232, 146, 146, 188, 240, 241, 199, 93, 223, 66, 177, 18, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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