Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b41c4569819046d636d6ff3dd654a85e315339664b99c8262470d5e01849daa5

Tx prefix hash: 6bf24aabacdb255f831ccb4b49515feb0fabda98ddf4a6b518db316dbf317fed
Tx public key: d0a6e5508321006514e8f38607a83a13f5e279ef739d5f97651365d8efd6c0e3
Timestamp: 1679822666 Timestamp [UCT]: 2023-03-26 09:24:26 Age [y:d:h:m:s]: 01:235:15:29:32
Block: 725369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 429252 RingCT/type: yes/0
Extra: 01d0a6e5508321006514e8f38607a83a13f5e279ef739d5f97651365d8efd6c0e3021100000001b3164c24000000000000000000

1 output(s) for total of 2.424104089000 dcy

stealth address amount amount idx
00: 7a4ce1d4e34ce94b08317a4a026e2b773a781be1c092f4bb1dc50a85463d9248 2.424104089000 1170478 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": 725379, "vin": [ { "gen": { "height": 725369 } } ], "vout": [ { "amount": 2424104089, "target": { "key": "7a4ce1d4e34ce94b08317a4a026e2b773a781be1c092f4bb1dc50a85463d9248" } } ], "extra": [ 1, 208, 166, 229, 80, 131, 33, 0, 101, 20, 232, 243, 134, 7, 168, 58, 19, 245, 226, 121, 239, 115, 157, 95, 151, 101, 19, 101, 216, 239, 214, 192, 227, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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