Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee1e543e0ddb483da794d0efa0a01b6e69fae7218c8ce30d324ffa266e043f1d

Tx prefix hash: 87590ffe0ccb9a379f410c5aed264188217b7156fa44aafb645c96bbfaa6109b
Tx public key: c0caa421412af625a09a4577f6a1396a83ad240eab704249f2034b28d3a7ddd2
Timestamp: 1715229770 Timestamp [UCT]: 2024-05-09 04:42:50 Age [y:d:h:m:s]: 01:004:08:44:54
Block: 1018010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264040 RingCT/type: yes/0
Extra: 01c0caa421412af625a09a4577f6a1396a83ad240eab704249f2034b28d3a7ddd20211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 461c325714d7e76128ab1c6e27f5aa3fe1070b0704247a48dc797d806ed0a0c4 0.600000000000 1481795 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": 1018020, "vin": [ { "gen": { "height": 1018010 } } ], "vout": [ { "amount": 600000000, "target": { "key": "461c325714d7e76128ab1c6e27f5aa3fe1070b0704247a48dc797d806ed0a0c4" } } ], "extra": [ 1, 192, 202, 164, 33, 65, 42, 246, 37, 160, 154, 69, 119, 246, 161, 57, 106, 131, 173, 36, 14, 171, 112, 66, 73, 242, 3, 75, 40, 211, 167, 221, 210, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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