Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40fab0a6306cbd28755fea21837d5f7c177bc3cc7a5c0229834b61b9b9c635de

Tx prefix hash: 9aa046e76c1d7c6897dd7aad9c238eaaeec86749f4037668a8734265fc84d2b6
Tx public key: 333f9e3e511c282912cc08f9344a05c90438c9a58483c89baeedc7e5fcb3aab1
Timestamp: 1734622204 Timestamp [UCT]: 2024-12-19 15:30:04 Age [y:d:h:m:s]: 00:016:14:25:32
Block: 1178695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11852 RingCT/type: yes/0
Extra: 01333f9e3e511c282912cc08f9344a05c90438c9a58483c89baeedc7e5fcb3aab1021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 460baa0d8fce623bdb9815a91f2e5e2e9a3997ff126c6d79134e8faa238dbd71 0.600000000000 1665084 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": 1178705, "vin": [ { "gen": { "height": 1178695 } } ], "vout": [ { "amount": 600000000, "target": { "key": "460baa0d8fce623bdb9815a91f2e5e2e9a3997ff126c6d79134e8faa238dbd71" } } ], "extra": [ 1, 51, 63, 158, 62, 81, 28, 40, 41, 18, 204, 8, 249, 52, 74, 5, 201, 4, 56, 201, 165, 132, 131, 200, 155, 174, 237, 199, 229, 252, 179, 170, 177, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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