Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1bc5963c81b7c1191bebd18b0436aa931de4399058ba8286a64d84cf27f6f7b

Tx prefix hash: d6308a601d59f9537a721f7377cc47be32ba69dbbef94efc32e296f597888796
Tx public key: c6a340f0a17ddb4c932f9f5400d91a311d6c7736de121fd20e6a27012d4b2f5b
Timestamp: 1583631878 Timestamp [UCT]: 2020-03-08 01:44:38 Age [y:d:h:m:s]: 04:269:20:51:08
Block: 78250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1087750 RingCT/type: yes/0
Extra: 01c6a340f0a17ddb4c932f9f5400d91a311d6c7736de121fd20e6a27012d4b2f5b02110000001681a90efe000000000000000000

1 output(s) for total of 337.851661760000 dcy

stealth address amount amount idx
00: 9799422b748d04c3559dc24454a4b726276a9c38f5b06e7d09a0d7eff07f14fd 337.851661760000 143694 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": 78260, "vin": [ { "gen": { "height": 78250 } } ], "vout": [ { "amount": 337851661760, "target": { "key": "9799422b748d04c3559dc24454a4b726276a9c38f5b06e7d09a0d7eff07f14fd" } } ], "extra": [ 1, 198, 163, 64, 240, 161, 125, 219, 76, 147, 47, 159, 84, 0, 217, 26, 49, 29, 108, 119, 54, 222, 18, 31, 210, 14, 106, 39, 1, 45, 75, 47, 91, 2, 17, 0, 0, 0, 22, 129, 169, 14, 254, 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