Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4866517249f70864422eb12fe8a1fdefd7fddaa938259ea2d060f61911005d77

Tx prefix hash: 558b1808a4e3033768f3b9663c56293f8f99bba8c8c8ab281f8e04eaf85b30c4
Tx public key: c4984ef89b9bfaeee8f3bc9f29836907a8eac5560df0197eea0d5f8798f8e73b
Timestamp: 1696703940 Timestamp [UCT]: 2023-10-07 18:39:00 Age [y:d:h:m:s]: 01:255:06:05:34
Block: 864619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 443389 RingCT/type: yes/0
Extra: 01c4984ef89b9bfaeee8f3bc9f29836907a8eac5560df0197eea0d5f8798f8e73b021100000002faf35c9c000000000000000000

1 output(s) for total of 0.837834747000 dcy

stealth address amount amount idx
00: 4afcb8498a24fb22f1fc08296fd159dbf49ceb474dc7cd8df3b0d770e3bee943 0.837834747000 1319139 of 0

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": 864629, "vin": [ { "gen": { "height": 864619 } } ], "vout": [ { "amount": 837834747, "target": { "key": "4afcb8498a24fb22f1fc08296fd159dbf49ceb474dc7cd8df3b0d770e3bee943" } } ], "extra": [ 1, 196, 152, 78, 248, 155, 155, 250, 238, 232, 243, 188, 159, 41, 131, 105, 7, 168, 234, 197, 86, 13, 240, 25, 126, 234, 13, 95, 135, 152, 248, 231, 59, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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