Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31f8920a995c75e446aa0a9a2b273c109bf70200fb45acdad07c5ddf60df3d2b

Tx prefix hash: fa2763a3b9e949e6a519cf5e70b2e1ac4d4f4454cce2b16fc8e77628466c43d3
Tx public key: 92f811bd33b6232d95e28a3a6d1b030387ec5e42ea231d1732b1d9e33451a8c8
Timestamp: 1580976378 Timestamp [UCT]: 2020-02-06 08:06:18 Age [y:d:h:m:s]: 04:362:04:49:09
Block: 59637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1150150 RingCT/type: yes/0
Extra: 0192f811bd33b6232d95e28a3a6d1b030387ec5e42ea231d1732b1d9e33451a8c802110000000456c366d3000000000000000000

1 output(s) for total of 389.402451548000 dcy

stealth address amount amount idx
00: 5a78f7aa2bed483eb77d6ec748406ce73ec1b5863fb4a685a7b9ffc6ea518654 389.402451548000 110092 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": 59647, "vin": [ { "gen": { "height": 59637 } } ], "vout": [ { "amount": 389402451548, "target": { "key": "5a78f7aa2bed483eb77d6ec748406ce73ec1b5863fb4a685a7b9ffc6ea518654" } } ], "extra": [ 1, 146, 248, 17, 189, 51, 182, 35, 45, 149, 226, 138, 58, 109, 27, 3, 3, 135, 236, 94, 66, 234, 35, 29, 23, 50, 177, 217, 227, 52, 81, 168, 200, 2, 17, 0, 0, 0, 4, 86, 195, 102, 211, 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