Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4efd7362507e5012fce2b4b157bcbf2f0c8bb7546ba3ee3c5355436807ea46c2

Tx prefix hash: 4da6bdda1089bbb22fdba28470a43c853a0ec48b90754a6edc41c696cda34f2a
Tx public key: 9b2994662779b055cd46a6c630c69c98e84f13d05ee651e59cb53e986d4d41d7
Timestamp: 1722634365 Timestamp [UCT]: 2024-08-02 21:32:45 Age [y:d:h:m:s]: 01:094:17:07:11
Block: 1079391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326162 RingCT/type: yes/0
Extra: 019b2994662779b055cd46a6c630c69c98e84f13d05ee651e59cb53e986d4d41d702110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f013ebb65f9be87738c55c1d2adf4f64b3b5ee065e98558a7f9dc93a97929c2 0.600000000000 1552326 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": 1079401, "vin": [ { "gen": { "height": 1079391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f013ebb65f9be87738c55c1d2adf4f64b3b5ee065e98558a7f9dc93a97929c2" } } ], "extra": [ 1, 155, 41, 148, 102, 39, 121, 176, 85, 205, 70, 166, 198, 48, 198, 156, 152, 232, 79, 19, 208, 94, 230, 81, 229, 156, 181, 62, 152, 109, 77, 65, 215, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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