Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3b2f66e753084a30ba6b296c7041f3e3eeba25a4e3dcd4b6b9a14d624a4e5ae

Tx prefix hash: e51dde533afbf010ff375d1d8e358af792d0f8e55b8a665429d80f1bea881a8d
Tx public key: 8837abb692cc4b1e808faf59d389ce268f3bc0c9408f79e08a4e367bc4ee8d96
Timestamp: 1582435421 Timestamp [UCT]: 2020-02-23 05:23:41 Age [y:d:h:m:s]: 05:060:23:01:48
Block: 70644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1196825 RingCT/type: yes/0
Extra: 018837abb692cc4b1e808faf59d389ce268f3bc0c9408f79e08a4e367bc4ee8d9602110000000103d36d11000000000000000000

1 output(s) for total of 358.036996297000 dcy

stealth address amount amount idx
00: 2dee22fa8e8273eca100a5622dd431abe16886dff6d9d9ae3b247f4f0d533946 358.036996297000 130526 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": 70654, "vin": [ { "gen": { "height": 70644 } } ], "vout": [ { "amount": 358036996297, "target": { "key": "2dee22fa8e8273eca100a5622dd431abe16886dff6d9d9ae3b247f4f0d533946" } } ], "extra": [ 1, 136, 55, 171, 182, 146, 204, 75, 30, 128, 143, 175, 89, 211, 137, 206, 38, 143, 59, 192, 201, 64, 143, 121, 224, 138, 78, 54, 123, 196, 238, 141, 150, 2, 17, 0, 0, 0, 1, 3, 211, 109, 17, 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