Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c83d44052b363979a6bd690782b9f88bf15c2b069a4feea450f53b7cdbc14dc

Tx prefix hash: 28ab44db09ba2435fb094377552d70234e11a8fcf8d466907e28c1caf544ec6e
Tx public key: 7952965fd4f6fa46666da6b283286f22be19425cb1366d7ea7741c98c4957e8e
Timestamp: 1745344911 Timestamp [UCT]: 2025-04-22 18:01:51 Age [y:d:h:m:s]: 00:206:02:38:32
Block: 1267163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145030 RingCT/type: yes/0
Extra: 017952965fd4f6fa46666da6b283286f22be19425cb1366d7ea7741c98c4957e8e0211000000026c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7e61fa4b1455a02c3f206f64a053e69aedd209a7cd7c86c791c3b973f7665a4 0.600000000000 1754390 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": 1267173, "vin": [ { "gen": { "height": 1267163 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7e61fa4b1455a02c3f206f64a053e69aedd209a7cd7c86c791c3b973f7665a4" } } ], "extra": [ 1, 121, 82, 150, 95, 212, 246, 250, 70, 102, 109, 166, 178, 131, 40, 111, 34, 190, 25, 66, 92, 177, 54, 109, 126, 167, 116, 28, 152, 196, 149, 126, 142, 2, 17, 0, 0, 0, 2, 108, 152, 170, 61, 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