Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0867ec668b1f8f1b671050acf06e0299d416a7e6ec4e7fb16135813f46795864

Tx prefix hash: 2910b856f2b447306b087622e298c1c7b82b7899936ba41e7e53b99a390e998d
Tx public key: d8735175b3f323e8a3d7a0b6628c730b34ede8a876abf2e80cf10222531056c2
Timestamp: 1581702451 Timestamp [UCT]: 2020-02-14 17:47:31 Age [y:d:h:m:s]: 05:264:12:44:49
Block: 65164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1339444 RingCT/type: yes/0
Extra: 01d8735175b3f323e8a3d7a0b6628c730b34ede8a876abf2e80cf10222531056c202110000000203d36d11000000000000000000

1 output(s) for total of 373.323585194000 dcy

stealth address amount amount idx
00: 7d212253dedc803b025403e3649d507cf244407ea69cc9e9b4aac05fde4531c6 373.323585194000 120155 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": 65174, "vin": [ { "gen": { "height": 65164 } } ], "vout": [ { "amount": 373323585194, "target": { "key": "7d212253dedc803b025403e3649d507cf244407ea69cc9e9b4aac05fde4531c6" } } ], "extra": [ 1, 216, 115, 81, 117, 179, 243, 35, 232, 163, 215, 160, 182, 98, 140, 115, 11, 52, 237, 232, 168, 118, 171, 242, 232, 12, 241, 2, 34, 83, 16, 86, 194, 2, 17, 0, 0, 0, 2, 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