Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39f601ce7974dba7a200ce9557f6b933f32d0e069086ce3fe89bb9f5246ae359

Tx prefix hash: c93eeb4d445d7e1662cbe6c938f962f74b87840dda691a87b93836ce1f2d755a
Tx public key: 85cab3df9d892f612e491c86c0b9fc3837e2b44ee360c5bf02d74b6fe56b522c
Timestamp: 1574731878 Timestamp [UCT]: 2019-11-26 01:31:18 Age [y:d:h:m:s]: 05:182:00:41:31
Block: 17564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1272744 RingCT/type: yes/0
Extra: 0185cab3df9d892f612e491c86c0b9fc3837e2b44ee360c5bf02d74b6fe56b522c021100000006354bbe3b000000000000000000

1 output(s) for total of 536.789555760000 dcy

stealth address amount amount idx
00: fc0ec2be67c74d02ba5c1efa8651e5c99c33f98277fe8dd66c0a2786f0a334e0 536.789555760000 25716 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": 17574, "vin": [ { "gen": { "height": 17564 } } ], "vout": [ { "amount": 536789555760, "target": { "key": "fc0ec2be67c74d02ba5c1efa8651e5c99c33f98277fe8dd66c0a2786f0a334e0" } } ], "extra": [ 1, 133, 202, 179, 223, 157, 137, 47, 97, 46, 73, 28, 134, 192, 185, 252, 56, 55, 226, 180, 78, 227, 96, 197, 191, 2, 215, 75, 111, 229, 107, 82, 44, 2, 17, 0, 0, 0, 6, 53, 75, 190, 59, 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