Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5d66ba1d82009cd25520bf0e7f228e6fbe590c8dce0cd96aa1726564f962f5a

Tx prefix hash: 4d44e160c35c96e446ddf6002e2a7a90220cb8f2d8d748f4d9e7dc7776e683c4
Tx public key: e9b7f5749e47c45d9efcaad9c130204f1f65f10edd737264aefda81f74d2e5d5
Timestamp: 1708140230 Timestamp [UCT]: 2024-02-17 03:23:50 Age [y:d:h:m:s]: 01:036:20:44:24
Block: 959224 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287372 RingCT/type: yes/0
Extra: 01e9b7f5749e47c45d9efcaad9c130204f1f65f10edd737264aefda81f74d2e5d50211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 149a225e67e48e88c0ab6130557936f423808fe45561ea82a3017a8414219c30 0.600000000000 1418755 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": 959234, "vin": [ { "gen": { "height": 959224 } } ], "vout": [ { "amount": 600000000, "target": { "key": "149a225e67e48e88c0ab6130557936f423808fe45561ea82a3017a8414219c30" } } ], "extra": [ 1, 233, 183, 245, 116, 158, 71, 196, 93, 158, 252, 170, 217, 193, 48, 32, 79, 31, 101, 241, 14, 221, 115, 114, 100, 174, 253, 168, 31, 116, 210, 229, 213, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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