Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f10441b7420ca1f863e397ddf6ebe0a1888019e43be882c2433a34053b6912d4

Tx prefix hash: cf98bdeb1e82b5dea6032363dee14fdc4f18e4d1dcc7f90726a165d9e6d9c82b
Tx public key: 0ae715242e42ab18508e47ac609f4dbe811d04e9a07390ce03f2a8bfe5a5cbbd
Timestamp: 1717892718 Timestamp [UCT]: 2024-06-09 00:25:18 Age [y:d:h:m:s]: 00:339:16:28:46
Block: 1040080 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242794 RingCT/type: yes/0
Extra: 010ae715242e42ab18508e47ac609f4dbe811d04e9a07390ce03f2a8bfe5a5cbbd0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48ebcb12cd2d3e27bb62af43d37240e5ecf0cda080872049847cad4dd009c63c 0.600000000000 1508735 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": 1040090, "vin": [ { "gen": { "height": 1040080 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48ebcb12cd2d3e27bb62af43d37240e5ecf0cda080872049847cad4dd009c63c" } } ], "extra": [ 1, 10, 231, 21, 36, 46, 66, 171, 24, 80, 142, 71, 172, 96, 159, 77, 190, 129, 29, 4, 233, 160, 115, 144, 206, 3, 242, 168, 191, 229, 165, 203, 189, 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