Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 765ccc199fbd88bc95c766147539178e30b46667546060e19c9206946cadcf6a

Tx prefix hash: 2ef3e6c3aa7bfae26dff18001a4b5da9a95761bf5e6624fbfc12d6b4db751d17
Tx public key: d5fa1edcf117c5c0ee0d4bb6059341a1b4e57102afdf736b8907efc74cc9bec7
Timestamp: 1727957831 Timestamp [UCT]: 2024-10-03 12:17:11 Age [y:d:h:m:s]: 01:060:06:20:01
Block: 1123530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301486 RingCT/type: yes/0
Extra: 01d5fa1edcf117c5c0ee0d4bb6059341a1b4e57102afdf736b8907efc74cc9bec702110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e515e97e97e3893d2d6a5197f0c5a67f29a8accc12bdbc8d6da5fe4b30cdb3f0 0.600000000000 1606065 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": 1123540, "vin": [ { "gen": { "height": 1123530 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e515e97e97e3893d2d6a5197f0c5a67f29a8accc12bdbc8d6da5fe4b30cdb3f0" } } ], "extra": [ 1, 213, 250, 30, 220, 241, 23, 197, 192, 238, 13, 75, 182, 5, 147, 65, 161, 180, 229, 113, 2, 175, 223, 115, 107, 137, 7, 239, 199, 76, 201, 190, 199, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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