Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6ce219b4e1ef9796f152c07a4af3a0fd21f3083f6abd6ec6762b7debdb0bf00

Tx prefix hash: a77a217ac3480d2ea59b8343a6cd771b3623cfbce021ada399ca14eb30953964
Tx public key: d94ff2b2aa7b1e07734c20d731720d3cbd8a59e3bb8d94573f2fe75f2789739c
Timestamp: 1582435083 Timestamp [UCT]: 2020-02-23 05:18:03 Age [y:d:h:m:s]: 04:267:07:33:01
Block: 70630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1083623 RingCT/type: yes/0
Extra: 01d94ff2b2aa7b1e07734c20d731720d3cbd8a59e3bb8d94573f2fe75f2789739c0211000000027adf42d3000000000000000000

1 output(s) for total of 358.075240962000 dcy

stealth address amount amount idx
00: ef581e70f974077ed3c6069ba841b5e69c7fd5d3c8db5716d9904864e0902ecb 358.075240962000 130506 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": 70640, "vin": [ { "gen": { "height": 70630 } } ], "vout": [ { "amount": 358075240962, "target": { "key": "ef581e70f974077ed3c6069ba841b5e69c7fd5d3c8db5716d9904864e0902ecb" } } ], "extra": [ 1, 217, 79, 242, 178, 170, 123, 30, 7, 115, 76, 32, 215, 49, 114, 13, 60, 189, 138, 89, 227, 187, 141, 148, 87, 63, 47, 231, 95, 39, 137, 115, 156, 2, 17, 0, 0, 0, 2, 122, 223, 66, 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