Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa4441f14186b89bcb9590fa5991730c0269dfe7cae4bd1b00ef802c52940da1

Tx prefix hash: f175d347def4dfd99aab03057a431fdbc6b292604c2c837e90a7fe46ee5eed89
Tx public key: d012f94cfe897ae480fa2f5493f9df239caeb1202a79322a9878488613aa6e01
Timestamp: 1580480820 Timestamp [UCT]: 2020-01-31 14:27:00 Age [y:d:h:m:s]: 05:003:21:43:09
Block: 55833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1154649 RingCT/type: yes/0
Extra: 01d012f94cfe897ae480fa2f5493f9df239caeb1202a79322a9878488613aa6e0102110000000249b77a3d000000000000000000

1 output(s) for total of 400.869411088000 dcy

stealth address amount amount idx
00: b9368fa945383be9e0a907a84e9d10c28a5e6b71ae9faa50cfbc588880ca023c 400.869411088000 103016 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": 55843, "vin": [ { "gen": { "height": 55833 } } ], "vout": [ { "amount": 400869411088, "target": { "key": "b9368fa945383be9e0a907a84e9d10c28a5e6b71ae9faa50cfbc588880ca023c" } } ], "extra": [ 1, 208, 18, 249, 76, 254, 137, 122, 228, 128, 250, 47, 84, 147, 249, 223, 35, 156, 174, 177, 32, 42, 121, 50, 42, 152, 120, 72, 134, 19, 170, 110, 1, 2, 17, 0, 0, 0, 2, 73, 183, 122, 61, 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