Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11fbf814352501ebbf654cae5a0d94cc0e758c330b8c8214f388072b8dca2772

Tx prefix hash: 4a77b239dee2b7c867477f28f0f1318bf9454eff00a568e2a4b083d4b452202f
Tx public key: fa6bb784cd37086014250c840e7b6c706750e497d8bc25a95e72aa331b4ddf31
Timestamp: 1722509406 Timestamp [UCT]: 2024-08-01 10:50:06 Age [y:d:h:m:s]: 00:177:20:47:23
Block: 1078357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127207 RingCT/type: yes/0
Extra: 01fa6bb784cd37086014250c840e7b6c706750e497d8bc25a95e72aa331b4ddf31021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cee503f5ab26731d294eba3cbf7b9bfae06090a62a8df2a75919ac8c0cb56eb 0.600000000000 1550934 of 15

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": 1078367, "vin": [ { "gen": { "height": 1078357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cee503f5ab26731d294eba3cbf7b9bfae06090a62a8df2a75919ac8c0cb56eb" } } ], "extra": [ 1, 250, 107, 183, 132, 205, 55, 8, 96, 20, 37, 12, 132, 14, 123, 108, 112, 103, 80, 228, 151, 216, 188, 37, 169, 94, 114, 170, 51, 27, 77, 223, 49, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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