Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e13f66c4828b6525d9da837f24b7c9c443aab7aa35c0a94f4178429a771222d7

Tx prefix hash: 28f0ea43795b6f60fd3854f5fa90c2e86571177955fcb83b0c2febd3fc560a9b
Tx public key: fa057d9a0e2d5581c4396d15b4b7bce1a5a4fc5bc151b92aaafabd6ba3214d60
Timestamp: 1580785305 Timestamp [UCT]: 2020-02-04 03:01:45 Age [y:d:h:m:s]: 04:329:07:11:39
Block: 58064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126881 RingCT/type: yes/0
Extra: 01fa057d9a0e2d5581c4396d15b4b7bce1a5a4fc5bc151b92aaafabd6ba3214d60021100000003dcee4b4d000000000000000000

1 output(s) for total of 394.103857392000 dcy

stealth address amount amount idx
00: 652bd56a6bbe7c89aa70ac5c32a5fd28896e4bf1be5d916ffd932f4e7ecdfa1c 394.103857392000 107374 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": 58074, "vin": [ { "gen": { "height": 58064 } } ], "vout": [ { "amount": 394103857392, "target": { "key": "652bd56a6bbe7c89aa70ac5c32a5fd28896e4bf1be5d916ffd932f4e7ecdfa1c" } } ], "extra": [ 1, 250, 5, 125, 154, 14, 45, 85, 129, 196, 57, 109, 21, 180, 183, 188, 225, 165, 164, 252, 91, 193, 81, 185, 42, 170, 250, 189, 107, 163, 33, 77, 96, 2, 17, 0, 0, 0, 3, 220, 238, 75, 77, 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