Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57f665a4548385dca9bb0741bfd81af105c116408e064ca4e0fb20ae1008a4a3

Tx prefix hash: ce09cbf3bc4e736e777dbea38ecb3391f5f0c01a29068344b48d41d7e582dc9d
Tx public key: 65f7fb565c4ded964e28d472aae662c0a44384ad64714a999a0ed7567072811d
Timestamp: 1580567072 Timestamp [UCT]: 2020-02-01 14:24:32 Age [y:d:h:m:s]: 04:294:02:00:57
Block: 56499 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1101443 RingCT/type: yes/0
Extra: 0165f7fb565c4ded964e28d472aae662c0a44384ad64714a999a0ed7567072811d021100000003dcee4b4d000000000000000000

1 output(s) for total of 398.848951164000 dcy

stealth address amount amount idx
00: 6f9076106aa8491e236dfdfa8aa4c83f920a05831990fddc97ebccfccdedbbdd 398.848951164000 104214 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": 56509, "vin": [ { "gen": { "height": 56499 } } ], "vout": [ { "amount": 398848951164, "target": { "key": "6f9076106aa8491e236dfdfa8aa4c83f920a05831990fddc97ebccfccdedbbdd" } } ], "extra": [ 1, 101, 247, 251, 86, 92, 77, 237, 150, 78, 40, 212, 114, 170, 230, 98, 192, 164, 67, 132, 173, 100, 113, 74, 153, 154, 14, 215, 86, 112, 114, 129, 29, 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