Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e116e6d2eb1d3365064945e56d7c0523d12e407c893eec6014ef0c66ac6edbbc

Tx prefix hash: 932657f1a055a03da1cfb974210e24cea1279222a71bc9520fcdbc615c392c9f
Tx public key: 00c3d2fcdf68ef1558a6908d53a91522ba84ce6c2389217c24280870c9fd6651
Timestamp: 1578756036 Timestamp [UCT]: 2020-01-11 15:20:36 Age [y:d:h:m:s]: 04:356:14:25:53
Block: 43304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1144360 RingCT/type: yes/0
Extra: 0100c3d2fcdf68ef1558a6908d53a91522ba84ce6c2389217c24280870c9fd66510211000000054943cd9f000000000000000000

1 output(s) for total of 441.129858367000 dcy

stealth address amount amount idx
00: d7b6d44dc47d17a7d3421f07d1108fa0ad2cea793f63f9f4054be8fa5eda291a 441.129858367000 78363 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": 43314, "vin": [ { "gen": { "height": 43304 } } ], "vout": [ { "amount": 441129858367, "target": { "key": "d7b6d44dc47d17a7d3421f07d1108fa0ad2cea793f63f9f4054be8fa5eda291a" } } ], "extra": [ 1, 0, 195, 210, 252, 223, 104, 239, 21, 88, 166, 144, 141, 83, 169, 21, 34, 186, 132, 206, 108, 35, 137, 33, 124, 36, 40, 8, 112, 201, 253, 102, 81, 2, 17, 0, 0, 0, 5, 73, 67, 205, 159, 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