Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40a3fe59316ea4e2e0957435e08ed3fcdd00c5b8dbc75c2c8e5c3d0035ce7eba

Tx prefix hash: c04d84490679b744e3ea1aa3f7250ce41675a6fdafe05b9f161ce8f8fd802e99
Tx public key: c1490b779aa4b427c3aebb5a233b59fe4e809e6e289a682c7e511f1c5d126009
Timestamp: 1735004284 Timestamp [UCT]: 2024-12-24 01:38:04 Age [y:d:h:m:s]: 00:311:20:30:34
Block: 1181837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220377 RingCT/type: yes/0
Extra: 01c1490b779aa4b427c3aebb5a233b59fe4e809e6e289a682c7e511f1c5d1260090211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 664b917c0ca5ee19ca69843bed7d19a37ff1fd7d7efed4fc1c6039312ec5d94b 0.600000000000 1668266 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": 1181847, "vin": [ { "gen": { "height": 1181837 } } ], "vout": [ { "amount": 600000000, "target": { "key": "664b917c0ca5ee19ca69843bed7d19a37ff1fd7d7efed4fc1c6039312ec5d94b" } } ], "extra": [ 1, 193, 73, 11, 119, 154, 164, 180, 39, 195, 174, 187, 90, 35, 59, 89, 254, 78, 128, 158, 110, 40, 154, 104, 44, 126, 81, 31, 28, 93, 18, 96, 9, 2, 17, 0, 0, 0, 3, 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