Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4771a6b2a14e618246d378c5586f21d9bae5cc01e590ca6a2ee0aa7be835e6d

Tx prefix hash: 87f40e4aa8cf5ef5b468d7bab02665d48342d829eb7f94214be7101b277fb702
Tx public key: a837875c639623e32383f03fc97f06228ce346f32ae53d6b875bdf7facc1ae93
Timestamp: 1736370327 Timestamp [UCT]: 2025-01-08 21:05:27 Age [y:d:h:m:s]: 00:075:21:10:28
Block: 1193131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54014 RingCT/type: yes/0
Extra: 01a837875c639623e32383f03fc97f06228ce346f32ae53d6b875bdf7facc1ae930211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f281e726eb3b7840cb5c02b18b421fa941a494e1493825aeee94d547fd0bd401 0.600000000000 1679690 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": 1193141, "vin": [ { "gen": { "height": 1193131 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f281e726eb3b7840cb5c02b18b421fa941a494e1493825aeee94d547fd0bd401" } } ], "extra": [ 1, 168, 55, 135, 92, 99, 150, 35, 227, 35, 131, 240, 63, 201, 127, 6, 34, 140, 227, 70, 243, 42, 229, 61, 107, 135, 91, 223, 127, 172, 193, 174, 147, 2, 17, 0, 0, 0, 4, 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