Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f331037c601e8e85e532c25f4be8c9bfbc492330262c789ccc15a5874479066a

Tx prefix hash: cf9fc4dbc07348f2a1d2e43175f1682b304c459e501fca75cdbbd4f9807242f3
Tx public key: ce1e2f72c66f38c968c4df41a02007663da7d68b2478cdc1d20006f10799cb56
Timestamp: 1730039190 Timestamp [UCT]: 2024-10-27 14:26:30 Age [y:d:h:m:s]: 00:028:07:11:08
Block: 1140747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20209 RingCT/type: yes/0
Extra: 01ce1e2f72c66f38c968c4df41a02007663da7d68b2478cdc1d20006f10799cb56021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25ab88af5d88fe9cac1edc840ed8af098d1e0ae06e06cc8871d98ab1257e86c7 0.600000000000 1624550 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": 1140757, "vin": [ { "gen": { "height": 1140747 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25ab88af5d88fe9cac1edc840ed8af098d1e0ae06e06cc8871d98ab1257e86c7" } } ], "extra": [ 1, 206, 30, 47, 114, 198, 111, 56, 201, 104, 196, 223, 65, 160, 32, 7, 102, 61, 167, 214, 139, 36, 120, 205, 193, 210, 0, 6, 241, 7, 153, 203, 86, 2, 17, 0, 0, 0, 1, 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