Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a27f4f0e576730361b1dd57d0fc0a2d28a665c78818ddd5c176a60fdb0aa0fc

Tx prefix hash: 75319b89dc1a52e35c2b44d1457aed69a52ac9a96e5cfff11879c0d263ff3739
Tx public key: 9a460b03c749f330fe6464c3f663dd14b8edd8d51362b3eafca9dd3ee887a9c6
Timestamp: 1715044114 Timestamp [UCT]: 2024-05-07 01:08:34 Age [y:d:h:m:s]: 00:324:20:55:16
Block: 1016480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232200 RingCT/type: yes/0
Extra: 019a460b03c749f330fe6464c3f663dd14b8edd8d51362b3eafca9dd3ee887a9c60211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f226e294051659b4ec41a50587db40a99eacaee37bab38110ab0bdbb7089d797 0.600000000000 1480073 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": 1016490, "vin": [ { "gen": { "height": 1016480 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f226e294051659b4ec41a50587db40a99eacaee37bab38110ab0bdbb7089d797" } } ], "extra": [ 1, 154, 70, 11, 3, 199, 73, 243, 48, 254, 100, 100, 195, 246, 99, 221, 20, 184, 237, 216, 213, 19, 98, 179, 234, 252, 169, 221, 62, 232, 135, 169, 198, 2, 17, 0, 0, 0, 1, 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