Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc04ae073da07cfb56eb5018efff928a66a8f684e8b855d1a222fe5de6cf7b92

Tx prefix hash: 85894ed6713eec66bf09d947b4112ab05c66234783f0d0a29c2f83d8968d03b3
Tx public key: 5015f3f46e992661d13ee973f92b1d16e3e49297b6a892970843cecc9411d59d
Timestamp: 1575384788 Timestamp [UCT]: 2019-12-03 14:53:08 Age [y:d:h:m:s]: 05:089:06:32:45
Block: 21640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0967 kB
Tx version: 2 No of confirmations: 1207706 RingCT/type: yes/0
Extra: 015015f3f46e992661d13ee973f92b1d16e3e49297b6a892970843cecc9411d59d020d3930303100010000004dc89603

1 output(s) for total of 520.353609246000 dcy

stealth address amount amount idx
00: 73715d074223d9ad7e1501f2a5203e97e1856750e1b87c479892ad203ff053b4 520.353609246000 34291 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": 21650, "vin": [ { "gen": { "height": 21640 } } ], "vout": [ { "amount": 520353609246, "target": { "key": "73715d074223d9ad7e1501f2a5203e97e1856750e1b87c479892ad203ff053b4" } } ], "extra": [ 1, 80, 21, 243, 244, 110, 153, 38, 97, 209, 62, 233, 115, 249, 43, 29, 22, 227, 228, 146, 151, 182, 168, 146, 151, 8, 67, 206, 204, 148, 17, 213, 157, 2, 13, 57, 48, 48, 49, 0, 1, 0, 0, 0, 77, 200, 150, 3 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8