Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d87ee169e0cfaf63de45e1042cbd36a083d3c791a475ecf21f0aefa0380f7db7

Tx prefix hash: 9b7b0619e534271358a5fa5e7d55aa1458596aca7468bf971ef8130ac4af0ab5
Tx public key: c7d04c7fbf02e8c7ea2a3202f65092b96b7d44ce6f79714201adaadaabe9d514
Timestamp: 1700266783 Timestamp [UCT]: 2023-11-18 00:19:43 Age [y:d:h:m:s]: 01:161:11:17:02
Block: 893956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376603 RingCT/type: yes/0
Extra: 01c7d04c7fbf02e8c7ea2a3202f65092b96b7d44ce6f79714201adaadaabe9d5140211000000014b8f5122000000000000000000

1 output(s) for total of 0.669811601000 dcy

stealth address amount amount idx
00: 18ca627e3773a334e770d4a97304235fd592beeb50b819497246d903e462210a 0.669811601000 1350141 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": 893966, "vin": [ { "gen": { "height": 893956 } } ], "vout": [ { "amount": 669811601, "target": { "key": "18ca627e3773a334e770d4a97304235fd592beeb50b819497246d903e462210a" } } ], "extra": [ 1, 199, 208, 76, 127, 191, 2, 232, 199, 234, 42, 50, 2, 246, 80, 146, 185, 107, 125, 68, 206, 111, 121, 113, 66, 1, 173, 170, 218, 171, 233, 213, 20, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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